Information retrieval method, information retrieval apparatus, and computer product

ABSTRACT

An information retrieval apparatus including a first detecting unit that detects a feeder indicative of a presence of a numerical value in a file subject to retrieval in which a numeral and a character are present together; a second detecting unit that detects a number of places in the numerical value correlated to the feeder detected by the first detecting unit; and a compressing unit that compresses the numerical value into compressed information including a compression code for a numeral indicative of the number of places detected by the second detecting unit and a compression code for a numeral at each place in the numerical value, wherein the numerical value is correlated to the feeder based on an appearance frequency of a numeral included in the file.

This application is a divisional of U.S. patent application Ser. No.12/418,886, filed Apr. 6, 2009, which is now U.S. Pat. No. 8,131,721,which is a U.S. Continuation Application of International ApplicationNo. PCT/JP2006/320827, filed Oct. 19, 2006.

FIELD

The embodiments discussed herein are related to a technique ofincreasing the speed of numerical value matching retrieval, numericalvalue range retrieval, and numerical value abstracted retrieval withrespect to numerical value data.

BACKGROUND

In conventional full text retrieval, an index is made for characterstrings to execute high-speed retrieval; however, no index is made fornumerical values. Further, although comparison for matching numericalcharacter strings is performed, comparison for matching numerical valuesis not. For example, different numerical expressions such as a stringincluding two-byte numerals “6 8 5 0

” and a string including one-byte numerals “

6,850” are determined to be “not matching” when compared as numericalcharacter strings notwithstanding the fact that both express anidentical numerical value.

The Electronic Ledger Storage Law stipulates that a forms system musthave a retrieval function suitable for designation of a numerical range,such as that, for example, disclosed in Japanese Laid-Open PatentApplication Publication No. H3-19081. Electronic ledgers areconventionally stored in a compressed/encoded form for data volumereduction and security.

Thus, in numerical value retrieval with respect to stored electronicledgers, a file of each ledger is decompressed and decoded, and iscompared in size with each numerical value of the data. This processrequires enormous hardware resources and extensive processing time.Relevant full text retrieval methods are classified into the followingthree types, the respective speeds of numerical retrieval for whichcannot be improved.

Advanced-index, full-text retrieval: In full text retrieval with respectto the Internet, an advanced index is used to increase retrieval speed.However, numerical value retrieval requires an index of an even greatersize, and is, therefore, not improved in terms of retrieval speed withthis retrieval method.

Simplified-index, full-text retrieval: This retrieval method increasesthe speed of full text retrieval using a simplified index, such as acharacter composition table for kanji; however, the speed of numericalvalue retrieval does not increase.

Indexless full-text retrieval: This method involves performing characterstring checks with respect to all data using a high-speed retrievalengine, but does not increase the speed of numerical value retrieval.

However, with the numerical value matching retrieval according to theconventional techniques above, faster retrieval speeds cannot beachieved for matching retrieval with respect to noncompressed/nonencodednumerical values, which leads to extremely time-consuming numericalvalue matching retrieval. In addition, the conventional numerical valuematching retrieval does not determine different numerical expressionssuch as “6 8 5 0

” and “

6,850” to be “matching”, bringing about a need for faster matchingretrieval using a simplified index and an improved method of determining“matching”.

When numerical value matching retrieval is performed with respect tocompressed/encoded numerical values according to conventional matchingretrieval, electronic ledger data, etc., which has been compressed andencoded for storage and security, are subject to size comparison afterdecompression and decoding; thereby requiring a large amount ofprocessing time. Therefore, a problem arises in that improving retrievalspeed involves revision of decompression and decoding processes.

When numerical value range retrieval is performed with respect tononcompressed/nonencoded numerical values according to conventionalmatching retrieval, a problem arises in that faster retrieval involvesusing a simplified index, similar to the above case of “numerical valuematching retrieval”.

When numerical value range retrieval is performed with respect tocompressed/encoded numerical values according to conventional rangeretrieval, a problem arises in that improving retrieval speed involvesrevision of decompression and decoding processes, similar the above caseof “numerical value matching retrieval”.

With no particular method found in the conventional technique,abstracted retrieval with respect to numerical values concerningclinical test data, etc., involves alteration of numerical value rangeretrieval mixed with human judgment and a combination of variousretrievals. Hence, the establishment of a technique for data abstractionand improved retrieval speed are desirable.

SUMMARY

According to an aspect of an embodiment, a computer-readable recordingmedium stores therein an information retrieval program that causes acomputer to execute acquiring a numerical value defining a boundary of anumerical value range; detecting a number of places in and a headnumeral of the numerical value acquired at the acquiring; extractingfrom a group of bit strings indicating, according to file, whethernumerical values in a numerical value group meeting a number of placesand a head numeral are present in files subject to retrieval, a bitstring indicating, according to file, whether a numerical value in anumerical value group having the number of places and the head numeraldetected at the detecting is present in files subject to retrieval;specifying, among the files subject to retrieval, a file correspondingto a bit in the bit string extracted at the extracting, the bitindicating a presence of a numerical value of the numerical value grouphaving the number of places and the head numeral detected at thedetecting; determining whether an in-file numerical value included inthe file specified at the specifying meets a boundary condition of thenumerical value defining the boundary; and designating, as a file havinga numerical value within the numerical value range, the file specifiedat the specifying, based on a determination result obtained at thedetermining.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram of an information retrieval apparatusaccording to an embodiment;

FIG. 2 is a diagram of a data configuration of electronic forms;

FIG. 3 is a diagram of file configuration data depicted in FIG. 2;

FIG. 4 is a diagram of page list data depicted in FIG. 2;

FIG. 5 is a diagram of appearance frequency management data;

FIG. 6 is a functional diagram of an information retrieval apparatusaccording to an embodiment;

FIG. 7 is a functional diagram of an appearance frequency managementdata generating unit depicted in FIG. 6;

FIG. 8 is a schematic of a process of generating the appearancefrequency management data;

FIG. 9 is a schematic of consecutive characters/non-standard charactersubstitution processing;

FIG. 10 is a diagram of a substitution table generated ultimately;

FIG. 11 is a functional diagram of a compressing/encoding unit depictedin FIG. 6;

FIG. 12 is a diagram of an example of revision of the appearancefrequency of a numeral, etc.;

FIG. 13 is a diagram of another example of revision of the appearancefrequency of a numeral, etc.;

FIG. 14 is a diagram of a Huffman tree generating process by thecompressing/encoding unit;

FIG. 15 is a functional diagram of a file compressing unit depicted inFIG. 11;

FIG. 16A is a diagram of a first example of a numerical valuecompressing process;

FIG. 16B is a diagram of a second example of the numerical valuecompressing process;

FIG. 16C is a diagram of a third example of the numerical valuecompressing process;

FIG. 16D is a diagram of an example of a process of compressingnumerical value abstracted data;

FIG. 17A is a diagram of a data configuration of a compressed forms fileresulting from compression by the file compressing unit;

FIG. 17B is a table of a comparison between the compressed block data C1to Cm and the original block data before compression;

FIG. 18 is a functional diagram of a retrieval initializing unitdepicted in FIG. 6;

FIG. 19 is a diagram of the corresponding relation between a characterrow/column correspondence table and an appearance map;

FIG. 20 is a diagram of the corresponding relation between a numericalvalue row/column correspondence table and the appearance map;

FIG. 21 is a functional diagram of a full text retrieval executing unitin the retrieval executing unit;

FIG. 22 is a diagram of an example of narrowing down compressed formsfiles to a compressed forms file Fi;

FIG. 23 is a diagram of a no-matching check process carried out by thefull text retrieval executing unit;

FIG. 24 is a table of shift operation of shifting compressed block dataof FIG. 23;

FIG. 25 is a diagram of a process of generating a preliminary checktable;

FIG. 26 is a diagram of an all bits no-matching check process;

FIG. 27 is a functional diagram of a numerical value retrieval executingunit in the retrieval executing unit;

FIGS. 28A to 28D are explanatory diagrams of examples of size comparisonin a numerical value range;

FIG. 29 is a functional diagram of a retrieval result display unitdepicted in FIG. 6;

FIG. 30 is a flowchart of an information retrieval process by theinformation retrieval apparatus according to the embodiment of thepresent invention;

FIG. 31 is a flowchart of the appearance frequency management datagenerating process (step S3001) of FIG. 30;

FIG. 32A is a (first half) flowchart of a numerical value/characterappearance frequency totaling process (step S3102);

FIG. 32B is a (second half) flowchart of the numerical value/characterappearance frequency totaling process (step S3102);

FIG. 33 is a flowchart of a compressing/encoding process (step S3002) ofFIG. 30;

FIG. 34 is a flowchart of a compressing process of step S3308 of FIG.33;

FIG. 35 is a flowchart of a retrieval initializing process (step S3303)of FIG. 30;

FIG. 36 is a flowchart of the retrieval process (step S3004) of FIG. 30;

FIG. 37 is a flowchart of a preliminary check table generating process;

FIG. 38 is a flowchart of a process of determining no matching ofcompressed block data with respect to a compressed keyword;

FIG. 39 is a flowchart of an all bits no-matching check process (stepS3812 and step S3817);

FIG. 40 is a flowchart of a numerical value retrieval executing processin a numerical value retrieval mode according to the embodiment of thepresent invention;

FIG. 41 is a flowchart of a lower limit specifying/comparing process ofFIG. 40;

FIG. 42 is a flowchart of a lower limit numerical value check process;

FIG. 43 is a flowchart of an upper limit specifying/comparing process ofFIG. 40; and

FIG. 44 is a flowchart of an upper limit numerical value check process.

DESCRIPTION OF EMBODIMENT(S)

Preferred embodiments of the present invention will be explained withreference to the accompanying drawings.

FIG. 1 is a block diagram of an information retrieval apparatusaccording to an embodiment.

As depicted in FIG. 1, an information retrieval apparatus includes acentral processing unit (CPU) 101, a read-only memory (ROM) 102, arandom access memory (RAM) 103, a hard disk drive (HDD) 104, a hard disk(HD) 105, a flexible disk drive (FDD) 106, a flexible disk (FD) 107, adisplay 108, an interface (I/F) 109, a keyboard 110, a mouse 111, ascanner 112, and a printer 113, connected to one another by way of a bus100.

The CPU 101 governs overall control of the information retrievalapparatus. The ROM 102 stores therein programs such as a boot program.The RAM 103 is used as a work area of the CPU 101. The HDD 104, underthe control of the CPU 101, controls the reading and writing of datawith respect to the HD 105. The HD 105 stores therein the data writtenunder control of the HDD 104.

The FDD 106, under the control of the CPU 101, controls the reading andwriting of data with respect to the FD 107. The FD 107 stores thereinthe data written under control of the FDD 106, the data being read bythe information retrieval apparatus.

In addition to the FD 107, a compact disc-read-only memory (CD-ROM)(compact disc-recordable (CD-R), compact disc-rewritable (CD-RW)),magneto optical disk (MO), digital versatile disk (DVD), a memory card,etc. may be adopted as a removable recording medium. The display 108displays, for example, data such as text, images, functionalinformation, etc., in addition to a cursor, icons, and/or tool boxes. Acathode ray tube (CRT), a thin-film-transistor (TFT) liquid crystaldisplay, a plasma display, etc., may be employed as the display 108.

The I/F 109 is connected to a network 114 such as the Internet through acommunication line and is connected to other apparatuses through thenetwork 114. The I/F 109 administers an internal interface with thenetwork 114 and controls the input/output of data from/to externalapparatuses. For example, a modem or a LAN adaptor may be employed asthe I/F 109.

The keyboard 110 includes, for example, keys for inputting letters,numerals, and various instructions and performs the input of data.Alternatively, a touch panel-type input pad or numeric keypad, etc. maybe adopted. The mouse 111 performs the movement of the cursor, selectionof a region, or movement and size change of windows. A track ball or ajoy stick may be adopted provided each respectively has a functionsimilar to a pointing device.

The scanner 112 optically reads an image and takes in the image datainto the information retrieval apparatus. The scanner 112 may have anoptical character recognition (OCR) function as well. The printer 113prints image data and text data. The printer 113 may be, for example, alaser printer or an ink jet printer.

FIG. 2 is a diagram of a data configuration of electronic forms. In thepresent specification, the electronic forms depicted in FIG. 2 representledgers and forms converted into electronic data. Contents 200 of theelectronic forms are saved in a superior folder 201, which includessubordinate folders consisting of a management folder 202 and a formsfolder 203.

The management folder 202 stores therein file configuration data 300(see FIG. 3), page list data 400 (see FIG. 4), and appearance frequencymanagement data 500 (see FIG. 5). The forms folder 203 stores therein aforms file group f including forms files fi (i=0 to n).

The forms files fi have forms data gj (j=1 to P), where the forms filesf0 to fn collectively have P pages of forms data gj in total. The formsdata gj is formatted in, for example, the HyperText Markup Language(HTML) format or the Extensible Markup Language (XML) format, andincludes various item data, such as a header segment (address data)including an anchor and a headword, article name data, quantity data,amount data, a subtotal segment, a total segment, and a trailer segment.

FIG. 3 is a diagram of the file configuration data 300 depicted in FIG.2. The file configuration data 300 is data correlating a file path foreach of the forms files f0 to fn for each file number i (i=0 to n). InFIG. 3, a forms file fi having a file number i is expressed as“file(i).html”.

FIG. 4 is a diagram of the page list data 400 depicted in FIG. 2. Thepage list data 400 is data correlating the forms files fi, the formsdata gj, and the file configuration data 300 depicted in FIG. 2. Thepage list data 400 includes the total number of forms files fi (n+1), ablock size (m byte), the total number of forms data gj (P), file pathdata FP(0) to FP(n) for the forms files fi, and a page list.

The page list data 400 further includes a file number i, the number ofblocks, and a file path as depicted in FIG. 3 for each file path dataFP(i). The page list 401 is a list in which offset, length, a pagenumber j, and a headword are described for each file number i.

FIG. 5 is a diagram of the appearance frequency management data 500. Asdepicted in FIG. 5, the appearance frequency management data 500 is datafor management of the appearance frequency of numerical value/characterdata. Numerical value/character data is classified into numerical valuedata and character data. Numerical value data is data including numeralsof 0 to 9, consecutive numerals consisting of a series of two or morenumerals, such as 00 to 99, numerical value groups each consisting ofnumerical values having the same number of places (digits) and the samehead numeral, and abstracted numerical value data of which numericalvalues give abstractive expressions, such as slightly high bloodpressure.

A numerical value group is a group of numerical values within anumerical value range defined by the number of places and a headnumeral. For example, a numerical value group defined by the number ofplaces of three and a headword of 2 is a group of numerical valueswithin a numerical value range of 200 to 299.

Character data is data including English characters, kana, kanji, andconsecutive characters. Specifically, character data include Englishcharacters, katakana, and symbols based on an 8-bit character-encodingscheme (ASCII); English characters, katakana, and symbols based on a16-bit character-encoding scheme (JIS); and kana and kanji based on the16-bit character-encoding scheme (JIS). In the present specification,these character data of phonogram and kanji centering around 8-bit codedata, such as English characters, kana, and katakana, are referred to as“standard character data”.

Character data also includes non-standard characters and consecutivecharacters, in addition to the standard character data. Consecutivecharacters represent character data of a string of two or morecharacters. For example, when two kanas each notated by a 16-bit codemake up consecutive characters, the consecutive characters representcharacter data notated by a 32-bit code. Binary data of an addresspointer, etc., is also included in the above “character data” forconvenience, although such binary data is non-character data.Hereinafter, binary data is included in “character data” in terminologyunless a specific notation is made.

The appearance frequency management data 500 includes the appearancefrequency, the number of appearance files (or number of blocks), anappearance rank, and appearance maps 510 (501 to 509) of numericalvalue/character data. The appearance frequency is the frequency (numberof times) at which numerical value/character data appears in the formsfiles f0 to fn collectively. The number of appearance files is thenumber of forms files in which numerical value/character data appearsamong all the forms files f0 to fn. An appearance rank is a position ina ranking of appearance frequencies.

The appearance maps 510 are strings of bits, each string consisting ofn+1 bits arranged in the order of the forms files fi, and each bitindicating the presence/absence of numerical value/character data. InFIG. 5, the bit at the left end corresponds to the forms file f0 whilethe bit at the right end corresponds to the forms file fn.

For each bit, “1” indicates ON while “0” indicates OFF. Specifically,when a bit corresponding to a forms file fi is “1” on the appearancemaps 510 for a certain numerical value/character data, it means that thenumerical value/character data is present in the forms file fi. When thebit corresponding to the forms file fi is “0”, it means that thenumerical value/character data is not present in the forms file fi.

FIG. 6 is a functional diagram of an information retrieval apparatusaccording to an embodiment. As depicted in FIG. 6, an informationretrieval apparatus 600 includes an editing unit 601 and a retrievingunit 602.

The editing unit 601 includes a file configuration data extracting unit611, an appearance frequency management data generating unit 612, and acompressing/encoding unit 613. Although files of forms are an example ofa subject to be retrieved, data other than that of forms may be thesubject of retrieval provided the data includes numerical value data.

The file configuration data extracting unit 611 refers to the fileconfiguration data depicted in FIG. 3 and extracts the page list data400 depicted in FIG. 4 from the forms files f0 to fn. The appearancefrequency management data generating unit 612 generates the appearancefrequency management data 500 from the forms files f0 to fn, and furthergenerates a substitution table 640 for substituting consecutive numeralsor consecutive characters written in multiple forms files f0 to fn witha non-standard character. Hereinafter, consecutive numerals andconsecutive characters are collectively referred to as “consecutivecharacter data”.

The compressing/encoding unit 613 compresses the forms files f0 to fn togenerate a compressed forms file group F, and encodes the appearancefrequency management data 500 and the substitution table 640 to generateencoded appearance frequency management data 650 and an encodedsubstitution table 660.

The retrieving unit 602 includes a retrieval initializing unit 621, aretrieval executing unit 622, and a retrieval result display unit 623.The retrieval initializing unit 621 decodes the encoded appearancefrequency management data 650 and the encoded substitution table 660 toinitialize the retrieval performed by the retrieving unit 602.

The retrieval executing unit 622 executes retrieval processing using theappearance frequency management data 500 and the substitution table 640to generate a retrieval candidate list. Specifically, the retrievalexecuting unit 622 includes a full text retrieval executing unit 624that executes full text retrieval and a numerical value retrievalexecuting unit 625 that executes numerical value retrieval.

The full text retrieval executing unit 624 receives input of a retrievalkeyword and executes full text retrieval with respect to compressedforms files to generate a retrieval candidate list displaying the formsfile(s) fi corresponding to the retrieval keyword.

The numerical value retrieval executing unit 625 receives input of anumerical value or a numerical value range and executes numerical valueretrieval with respect to the compressed forms file group F to generatea retrieval candidate list displaying the forms file(s) fi correspondingto the input numerical value or numerical value range.

The retrieval result display unit 623 decompresses a retrieval candidateselected by a user from among the retrieval candidates given by theretrieval executing unit 622, and displays the decompressed retrievalcandidate as a retrieval result. Respective functions of the formsfiles, the appearance frequency management data 500, the fileconfiguration data 300, the page list data 400, the substitution table640, the compressed forms file group F, the encoded appearance frequencymanagement data 650, and the encoded substitution table 660 as describedare implemented, for example, through recording media, such as the ROM102, RAM 103, and HD 105 depicted in FIG. 1.

Respective functions of the editing unit 601 (including internalfunctional configuration) and the retrieving unit 602 (includinginternal functional configuration) are implemented, for example, whenthe CPU 101 executes a program recorded on a recording medium, such asthe ROM 102, RAM 103, and HD 105 depicted in FIG. 1.

FIG. 7 is a functional diagram of the appearance frequency managementdata generating unit 612 depicted in FIG. 6. As depicted in FIG. 7, theappearance frequency management data generating unit 612 includes anumerical value/character data extracting unit 701, a numericalvalue/character appearance frequency totaling unit 702, a sorting unit703, and a generation process unit 704.

The numerical value/character data extracting unit 701 extractsnumerical/character data sequentially from forms files. The numericalvalue/character appearance frequency totaling unit 702 totals therespective frequencies at which the numerical/character data extractedby the numerical value/character data extracting unit 701 appears in theforms files fi, and detects the presence/absence of thenumerical/character data in each of the forms files f0 to fn.

The sorting unit 703 sorts the numerical value/character data accordingto appearance frequency. The generating process unit 704 generates theappearance frequency management data 500, using the appearancefrequencies of the sorted numerical/character data and the appearancemaps 501 to 509 indicative of the result of presence/absence detectionfor each of numerical/character data. The generating process unit 704also generates the substitution table 640. A process of generating theappearance frequency management data 500 and the substitution table 640by the appearance frequency management data generating unit 612 will bedescribed in detail.

FIG. 8 is a schematic of the process of generating the appearancefrequency management data 500. Section A in FIG. 8 depicts a dataconfiguration of the appearance frequency management data 500 thatresults when the numerical value/character appearance frequency totalingunit 702 totals numerical value/character data. Section B in FIG. 8depicts a data configuration of the appearance frequency management data500 that results after consecutive characters/non-standard charactersubstitution processing. Section C in FIG. 8 depicts a dataconfiguration of the appearance frequency management data 500 thatresults after mixture data including standard character data andnon-standard character data are sorted. Section D in FIG. 8 depicts adata configuration of the appearance frequency management data 500 thatresults after mixture data with a low appearance frequency is cut out.Section E in FIG. 8 depicts a data configuration of the appearancefrequency management data 500 generated ultimately.

In section A of FIG. 8, reference numeral 800 denotes a management areaof the appearance frequency management data 500. Reference numeral 801denotes a numerical value area in which the appearance frequency, thenumber of appearance files, the appearance rank, and an appearance mapof numerical data (not including consecutive numerals) are stored.Reference numeral 802 denotes a standard character area in which theappearance frequency, the number of appearance files, the appearancerank, and an appearance map of standard character data are stored, thestandard character data including English characters, katakana, andsymbols based on an 8-bit character-encoding scheme (ASCII), Englishcharacters, katakana, and symbols based on a 16-bit character-encodingscheme (JIS), and kana and kanji based on the 16-bit character-encodingscheme (JIS).

Reference numeral 803 denotes a non-standard character area in which theappearance frequency, the number of appearance files, the appearancerank, and an appearance map of non-standard character data are stored.Reference numeral 804 denotes a consecutive characters area in which theappearance frequency, the number of appearance files, the appearancerank, and an appearance map of consecutive characters data are stored.Reference numeral 805 denotes a binary area in which the appearancefrequency, the number of appearance files, and the appearance rank of8-bit binary data are stored.

In the data configuration depicted in section A of FIG. 8, consecutivecharacters data in the consecutive characters area 804 are sorted in theorder of appearance frequency. Consecutive characters data having agiven appearance frequency or higher is substituted with non-standardcharacter data that do not coincide with existing non-standard characterdata (hereinafter, “consecutive characters/non-standard characterdata”). In this manner, consecutive characters data consisting of astring of characters with a high appearance frequency are replaced withnon-standard character data, which is single character data; therebyreducing data volume and thus improving compression efficiency.Consecutive characters data having an appearance frequency lower thanthe given appearance frequency is consecutive characters data that doesnot appear frequently. Such consecutive characters data is, therefore,fragmented into single character data, which are allocated tocorresponding areas. As a result, the data configuration of theappearance frequency management data 500 depicted in section A of FIG. 8becomes the data configuration depicted in section (B) resulting afterthe consecutive characters/non-standard character substitutionprocessing.

In the data configuration depicted in section B of FIG. 8, data in thenumerical value area 801, standard character data in the standardcharacter area 802, and non-standard character data in the non-standardcharacter area 803 are mixed, and are sorted in descending order ofappearance frequency, which results in the data configuration depictedin section C. In the data configuration depicted in section C,consecutive characters/non-standard character data in the consecutivecharacters/non-standard character area 814 and binary data in the binaryarea 805 of section B are not subject to sorting.

In the data configuration depicted in section C, data having a lowappearance frequency, such as data of zero appearance, is cut out from amixture area 812 in which numerical value data, standard character data,and non-standard character data are present together. Cutting out lowappearance frequency data results in the data configuration depicted insection D. In the data configuration depicted in section D, themanagement area 800 and the mixture area 812, the consecutivecharacters/non-standard character area 814, and the binary area 805 arecombined together to ultimately generate the appearance frequencymanagement data 500 having the data configuration depicted in section E.

In the appearance frequency management data 500, the management area 800stores therein the number of files/blocks, the number of types ofcharacter data that appear (number of appeared character data (type)),the number of consecutive characters/non-standard character data (numberof consecutive characters (256 types)), and the number of binary data(256 types).

In the appearance frequency management data 500 depicted in FIG. 5, withthe exception of binary data, appearance frequencies and the appearancemaps 510 are correlated with the numerical value/character data. Thenumerical value/character data is sorted in descending order ofappearance frequency. In the appearance frequency management data 500depicted in FIG. 5, the numerical value/character data and theappearance frequency thereof are encoded by an encoding algorithm ofexclusive-OR (XOR), etc., using a prescribed master key, which will bedescribed later.

FIG. 9 is a schematic of consecutive characters/non-standard charactersubstitution processing. In FIG. 9, section F depicts a dataconfiguration of the consecutive characters area 804 of the appearancefrequency management data 500 that results when consecutive charactersdata is totaled by the numerical value/character appearance frequencytotaling unit 702. Section G depicts a data configuration of theconsecutive characters area 804 that results after consecutivecharacters data is sorted. Section H depicts a data configuration thatresults after the substitution processing.

In the data configuration depicted in section F, the consecutivecharacters area 804 includes areas 901 to 907. The area 901 storestherein information concerning numerical string data (“00” to “99”) inthe 8-bit character-encoding scheme (ASCII) format; the informationincluding the numerical string data, the appearance frequency, thenumber of appearance files, the appearance rank, and an appearance map.

The area 902 stores therein information concerning English characterstring data (“AA” to “zz”) in the 8-bit character-encoding scheme(ASCII) format; the information including the English character stringdata, the appearance frequency, the number of appearance files, theappearance rank, and an appearance map. The area 903 stores thereininformation concerning katakana string data (“

” to “

”, voiced consonant, semi-voiced consonant) in the 8-bitcharacter-encoding scheme (ASCII) format; the information including thekatakana string data, the appearance frequency, the number of appearancefiles, the appearance rank, and an appearance map.

The area 904 stores therein information concerning numerical string data(“0 0” to “9 9”) in the 16-bit character-encoding scheme (JIS) format;the information including the numerical string data, the appearancefrequency, the number of appearance files, the appearance rank, and anappearance map. The area 905 stores therein information concerningEnglish character string data (“A A” to “z z”) in the 16-bitcharacter-encoding scheme (JIS) format; the information including theEnglish character string data, the appearance frequency, the number ofappearance files, the appearance rank, and an appearance map.

The area 906 stores therein information concerning katakana string data(“

” to “

”, voiced consonant, semi-voiced consonant) in the 16-bitcharacter-encoding scheme (JIS) format; the information including thekatakana string data, the appearance frequency, the number of appearancefiles, the appearance rank, and an appearance map. The area 907 storestherein information concerning kana string data (“

” or “

”, voiced consonant, semi-voiced consonant) in the 16-bitcharacter-encoding scheme (JIS) format; the information including thekana string data, the appearance frequency, the number of appearancefiles, the appearance rank, and an appearance map.

The data configuration depicted in section G of FIG. 9 is the result ofsorting consecutive characters data making up the data configurationdepicted in section F in descending order of appearance frequency. Inthe data configuration depicted in section G, an area 911 hasinformation concerning consecutive characters data having a highappearance frequency, which is to be substituted with non-standard data.An area 912, on the other hand, has information concerning consecutivecharacters data having an appearance frequency that is lower than thegiven appearance frequency (low appearance frequency consecutivecharacters data). This low appearance frequency consecutive charactersdata is fragmented into single character data. Hence, the appearancefrequency and the appearance maps 505 to 509 of character data arerevised.

The data configuration depicted in section H of FIG. 9 is the result ofsubstituting the high appearance frequency consecutive characters datain the data configuration depicted in section G with non-standardcharacter data. The consecutive characters/non-standard character area814 stores therein information concerning consecutivecharacters/non-standard character data resulting from the substitution;the information including the consecutive characters/non-standardcharacter data, the appearance frequency, the number of appearancefiles, the appearance rank, and an appearance map.

FIG. 10 is a diagram of the substitution table 640 generated ultimately.The substitution table 640 is generated by correlating the consecutivecharacters data in the area 911 of the data configuration depicted insection G of FIG. 9 and the consecutive characters/non-standardcharacter data in the area 814 of the data configuration depicted insection H of FIG. 9.

FIG. 11 is a functional diagram of the compressing/encoding unit 613depicted in FIG. 6. As depicted in FIG. 11, the compressing/encodingunit 613 includes an appearance frequency revising unit 1101, afragmenting unit 1102, an encoding unit 1103, an occurrence probabilitycalculating unit 1104, a Huffman tree generating unit 1105, and a filecompressing unit 1106.

The appearance frequency revising unit 1101 revises the appearancefrequency of numerals in the appearance frequency management data 500.Specifically, for example, the bit width of a compression code for anumeral such as 0 to 9, a decimal point, and a feeder (hereinafter“numeral, etc.”) is set and an appearance frequency corresponding to theset bit width is set for a numeral, etc., such as 0 to 9. Morespecifically, the appearance frequency of a numeral, etc., is revisedforcibly to be higher than the appearance frequency of character data.

FIG. 12 is a diagram of an example of revision of the appearancefrequency of a numeral, etc. FIG. 12 depicts a code table for revisingthe appearance frequency of numerical value/character data. As depictedin FIG. 12, the bit width of the compression code is 4 bits; hence, theappearance frequency of each numerical value, etc., is 1/16, to whichanother appearance frequency is further added according to theappearance rank of each numerical value, etc. The revision exampledepicted in FIG. 12 is effective in application to a forms file havingmany numerals. When the sum of appearance frequencies exceeds 1 as aresult of revision, the appearance frequency of other character data isrevised according to the corresponding appearance frequency thereof.

FIG. 13 is a diagram of another example of revision of the appearancefrequency of a numeral, etc. FIG. 13 depicts a code table for revisingthe appearance frequency of numerical value/character data. In FIG. 13,the bit width of the compression code is 5 bits; hence, the appearancefrequency of each numerical value, etc., is 1/32, to which anotherappearance frequency is further added according to the appearance rankof each numerical value, etc. The revision example depicted in FIG. 13is effective in application to a Web homepage having much characterdata. When the sum of appearance frequencies exceeds 1 as a result ofrevision, the appearance frequency of other character data is revisedaccording to the corresponding appearance frequency thereof.

The fragmenting unit 1102 depicted in FIG. 11 sorts numericalvalue/character data in the character area of the appearance frequencymanagement data 500 in descending order of appearance frequency.Numerical value/character data having a low appearance frequency, i.e.,an appearance frequency that is lower than a given appearance frequency,is fragmented into 8-bit code data and is stored in the binary areawhere 8-bit code binary data is stored.

The encoding unit 1103 encodes the appearance frequency management data500 resulting from data fragmenting by the fragmenting unit 1102 throughXOR processing, using a prescribed master key, to generate the encodedappearance frequency management data 650. The substitution table 640 mayalso be encoded through XOR processing, using a prescribed master key,to generate the encoded substitution table 660.

The occurrence probability calculating unit 1104 sorts numerical valuedata, standard character data, consecutive characters/non-standardcharacter data, and binary data in the appearance frequency managementdata 500 resulting from data fragmenting by the fragmenting unit 1102,in descending order of appearance frequency to calculate the occurrenceprobabilities of the data. The Huffman tree generating unit 1105generates a Huffman Tree from the occurrence probabilities calculated bythe occurrence probability calculating unit 1104.

The file compressing unit 1106 compresses the forms file group f usingthe Huffman tree generated by the Huffman tree generating unit 1105 togenerate the compressed forms file group F. Specifically, the filecompressing unit 1106 compresses the forms file group f by assigningshorter bits to numerical value/character data written in the formsfiles f0 to fn in descending order of post-amendment appearancefrequency, i.e., in descending order of occurrence probability. Thecompression of the forms file group f by the file compressing unit 1106is carried out by using compressing methods that differ for compressingnumerical values and character data, which will be described later.

FIG. 14 is a diagram of a Huffman tree generating process by thecompressing/encoding unit 613. In the appearance frequency managementdata 500 of a data configuration as depicted in FIG. 14, low appearancefrequency character data is fragmented by the fragmenting unit 1102, andthe fragmented character data is stored in the binary area storingbinary data (data configuration (J) of FIG. 14).

Subsequently, in the data configuration (J), all of numericalvalue/character data in the mixture area, in the consecutivecharacters/non-standard character area, and in the binary area aresorted in descending order of appearance frequency (data configuration(K) of FIG. 14). In an area 1400 of the data configuration of (K), theoccurrence probability of each of numerical value/character data iscalculated using the appearance frequency as a Huffman compressionparameter (data configuration (L) of FIG. 14). Finally, with the dataconfiguration (L), a Huffman tree is generated from the occurrenceprobability of each of numerical value/character data (dataconfiguration (M) of FIG. 14).

FIG. 15 is a functional diagram of the file compressing unit 1106depicted in FIG. 11.

As depicted in FIG. 15, the file compressing unit 1106 includes a feederdetecting unit 1501, a character data extracting unit 1502, a numericalvalue extracting unit 1503, a numerical value information detecting unit1504, and a compressing process unit 1505.

The feeder detecting unit 1501 detects a feeder in a forms file fi.Because a feeder is at the head of a numerical value, detection of thefeeder means the presence of the numerical value following the feeder.No detection of a feeder, therefore, means recognition of characterdata.

When the feeder detecting unit 1501 does not detect a feeder at a feederposition, the character data extracting unit 1502 extracts, as characterdata, data located at the position. The extracted character data issubjected to a compressing process at the compressing process unit 1505.

When the feeder detecting unit 1501 detects a feeder, the numericalvalue extracting unit 1503 extracts a numerical value correlated withthe feeder, e.g., a numerical string following the feeder, as anumerical value. When a comma or decimal point is included in thenumerical string, the comma or decimal point is also extracted.

The numerical value information detecting unit 1504 extracts detailedinformation concerning the numerical value extracted by the numericalvalue extracting unit 1503. The detailed information is, for example,information indicating the number of places of the numerical value,whether the numerical value is two-byte or one-byte, whether thenumerical value includes a comma or a decimal point, and the location ofthe decimal point if included.

The compressing process unit 1505, using the Huffman tree generated bythe Huffman tree generating unit 1105, compresses character dataextracted by the character data extracting unit 1502 and numerical valuedata extracted by the numerical value extracting unit 1503.

When numerical values are compressed, a numeral expressing the number ofplaces and a numeral in each place are each converted into a compressioncode corresponding to the numeral. Compression codes for numerals eachin each place are arranged in the order of the places. If a numericalvalue includes a decimal point, the numerical value is converted into acompression code corresponding to the decimal point. Thepresence/absence of a comma and two-byte/one-byte are each expressed by1 bit.

In a numerical value compressing process, only the numerical value isextracted from the numerical value information concerning a monetaryamount, blood pressure, etc. The extracted numerical value iscompressed. Specifically, a compression code for a feeder is read out,referring to the code tables depicted in FIGS. 12 and 13.

Subsequently, a bit indicative of whether the numerical value is atwo-byte numerical value or a one-byte numerical value(two-byte/one-byte bit) is set. This two-byte/one-byte bit is “1” whenthe numerical value is a two-byte numerical value, and is “0” when thenumerical value is a one-byte numerical value. A comma presence/absencebit indicative of whether the numerical value is expressed using a comma“,” is set. This comma presence/absence bit is “1” when the numericalvalue includes a comma, and is “0” when the numerical value includes nocomma.

The number of places of the numerical value is then detected. Thedetected number of places does not include the number of placesfollowing a decimal point. A compression code for a numeral equivalentto the detected number of places is read out of the code table depictedin FIG. 12. Compression codes for each numeral at each place from thehead place to the end place making up the numerical value are read outfrom the coding tables depicted in FIGS. 12 and 13.

When the numerical value includes a decimal point, a compression codefor the decimal point is read out from the coding tables depicted inFIGS. 12 and 13. In this manner, the numerical value is compressed intoa numerical string composed of compression codes and bits. An example ofa compressing process using the code table depicted in FIG. 12 will bedescribed hereinafter. A numerical value subjected to the compressingprocess is referred to as a compressed numerical value.

FIG. 16A is a diagram of a first example of a numerical valuecompressing process. As depicted in FIG. 16A,

at the head position and “-” at the end position are separated fromnumerical value information “

6,800.-” to extract a numerical value “6,800.”, which is compressed.

Specifically, a compression code “1011” for a feeder “x′B′” indicativeof the starting point of the numerical value is read out from the codetable depicted in FIG. 12. Subsequently, a two-byte/one-byte bit “0”indicative of the numerical value “6,800.” being a one-byte numericalvalue is set. A comma presence/absence bit “1” indicative of thenumerical value “6,800.” being expressed using a comma “,” is also set.The number of places “4” of the numerical value “6,800.” is thendetected, and a compression code “0100” for the detected number ofplaces “4” is read out from the code table depicted in FIG. 12.

Subsequently, compression codes “0110”, “1000”, “0000”, and “0000” forthe head numeral “6”, the second numeral “8”, the third numeral “0”, andthe end numeral “0” of the numerical value “6,800.” are read out fromthe code table depicted in FIG. 12. Lastly, a compression code “1010”for the decimal point “x′A′” of the numerical value “6,800.” is read outfrom the code table depicted in FIG. 12. The numerical value “6,800.” iscompressed in this manner.

FIG. 16B is a diagram of a second example of the numerical valuecompressing process. As depicted in FIG. 16B, “$” at the head positionand “-” at the end position are separated from numerical valueinformation “$680.50-” to extract a numerical value “680.50”, which iscompressed.

Specifically, the compression code “1011” for the feeder “x′B′”indicative of the starting point of the numerical value is read out fromthe code table depicted in FIG. 12. Subsequently, a two-byte/one-bytebit “0” indicative of the numerical value “680.50” being a one-bytenumerical value is set. A comma presence/absence bit “0” indicative ofthe numerical value “680.50” being expressed without using a comma “,”is also set. The number of places “3” of the numerical value “680.50” isthen detected, and a compression code “0011” for the detected number ofplaces “3” is read out from the code table depicted in FIG. 12.

Subsequently, compression codes “0110”, “1000”, “0000”, “1010”, “0101”,and “0000” for the head numeral “6”, the second numeral “8”, the thirdnumeral “0”, the decimal point “x′A′”, the fourth numeral “5”, and theend numeral “0” of the numerical value “680.50” are read out from thecode table depicted in FIG. 12. The numerical value “680.50” iscompressed in this manner.

FIG. 16C is a diagram of a third example of the numerical valuecompressing process. As depicted in FIG. 16C,

at the end position is separated from numerical value information “6 8 00

” to extract a numerical value “6 8 0 0”, which is compressed.

Specifically, the compression code “1011” for the feeder “x′B′”indicative of the starting point of the numerical value is read out fromthe code table depicted in FIG. 12. Subsequently, a two-byte/one-bytebit “1” indicative of the numerical value “6 8 0 0” being a two-bytenumerical value is set. A comma presence/absence bit “0” indicative ofthe numerical value “6 8 0 0” being expressed without using a comma “,”is also set. The number of places “4” of the numerical value “6 8 0 0”is then detected, and the compression code “0100” for the detectednumber of places “4” is read out from the code table depicted in FIG.12.

Subsequently, compression codes “0110”, “1000”, “0000”, and “0000” forthe head numeral “6”, the second numeral “8”, the third numeral “0”, andthe end numeral “0” of the numerical value “6 8 0 0” are read out of thecode table depicted in FIG. 12. The numerical value “6 8 0 0” iscompressed in this manner.

FIG. 16D is a diagram of an example of a process of compressingnumerical value abstracted data. As depicted in FIG. 16D, in HTML datadescription, “</minimum blood pressure>” at the head position and thesame at the end position are separated from numerical value abstracteddata representing a minimum blood pressure “<minimum bloodpressure>107<minimum blood pressure>” to extract a numerical value“107”, which is compressed.

Specifically, a compression code “00001011” for a feeder “x′0B′”indicative of the starting point of the numerical value is read out fromthe code table depicted in FIG. 12. The feeder “x′0B′” is a feeder thatidentifies the numerical value as the last blood pressure. Subsequently,a two-byte/one-byte bit “0” indicative of the numerical value “107”being a one-byte numerical value is set. A comma presence/absence bit“0” indicative of the numerical value “107” being expressed withoutusing a comma “,” is also set. The number of places “3” of the numericalvalue “107” is then detected, and the compression code “0011” for thedetected number of places “3” is read out from the code table depictedin FIG. 12.

Subsequently, compression codes “0001”, “0000”, and “0111” for the headnumeral “1”, the second numeral “0”, and the third numeral “7” of thenumerical value “107” are read out from the code table depicted in FIG.12. The numerical value “107” is compressed in this manner.

FIG. 17A is a diagram of a data configuration of a compressed forms fileresulting from compression by the file compressing unit 1106. Withreference to FIG. 17A, an arbitrary compressed forms file Fi will bedescribed. The compressed forms file Fi is made up of an area 1701storing therein information of the number of blocks (m), an area 1702storing therein address information (#1 to #m) of m blocks, and an area1703 storing therein compressed block data C1 to Cm of the blocks.

FIG. 17B is a table of a comparison between the compressed block data C1to Cm and the original block data before compression. As depicted inFIG. 17B, the lengths of the compressed block data C1 to Cm are reducedapproximately to the half of the lengths of the corresponding originalblock data through compression.

FIG. 18 is a functional diagram of the retrieval initializing unit 621depicted in FIG. 6. As depicted in FIG. 18, the retrieval initializingunit 621 includes a decoding unit 1801, a fragmenting unit 1802, anoccurrence probability calculating unit 1803, a Huffman tree generatingunit 1804, and an appearance map setting unit 1805.

The decoding unit 1801 decodes the encoded appearance frequencymanagement data 650. Specifically, the decoding unit 1801 executes adecoding process through exclusive-OR (XOR) using the encoding masterkey of FIG. 11. In the same manner, the decoding unit 1801 also decodesthe encoded substitution table 660 into the original substitution table640. The fragmenting unit 1802, the occurrence probability calculatingunit 1803, and the Huffman tree generating unit 1804 execute the sameprocess carried out by the fragmenting unit 1102, the occurrenceprobability calculating unit 1104, and the Huffman tree generating unit1105 depicted in FIG. 11 to generate a Huffman tree 1810, which is theHuffman tree that is revised by the appearance frequency revising unit1101.

The appearance map setting unit 1805 reads the appearance maps 510 ofthe decoded appearance frequency management data 500, and expands theread contents on a memory to link the contents to a row/columncorresponding table. The row/column (kuten) code is character code fortwo-byte characters established by Japanese Industrial Standards (JIS).The row/column corresponding table is the table on which the address ofeach line and column is stored.

FIG. 19 is a diagram of the corresponding relation between a characterrow/column correspondence table and the appearance map. A characterrow/column correspondence table 1900 correlates character data of theappearance frequency management data 500 with the appearance maps 505 to509. The appearance maps 505 to 509 representing strings of bitsindicative of the presence/absence of character data corresponding torows/columns can be called up, using the character row/columncorresponding table 1900.

FIG. 20 is a diagram of the corresponding relation between a numericalvalue row/column correspondence table and the appearance map. Anumerical value row/column correspondence table 2000 correlatesnumerical value groups of the appearance frequency management data 500with the appearance map 503. The appearance map 503 representing stringsof bits indicative of the presence/absence of numerals in numericalgroups corresponding to rows/columns can be called up, using thecharacter row/column corresponding table 2000.

FIG. 21 is a functional diagram of the full text retrieval executingunit 624 in the retrieval executing unit 622.

As depicted in FIG. 21, the full text retrieval executing unit 624includes a retrieval keyword input process unit 2101, a retrievalkeyword compressing unit 2102, an appearance map reading unit 2103, acompressed forms file specifying unit 2104, a compressed forms fileextracting unit 2105, a determining unit 2106, a block decompressingunit 2107, a character string comparing unit 2108, a file configurationdata specifying unit 2109, a retrieval candidate list display unit 2110,and a retrieval candidate selecting unit 2111.

The retrieval keyword input process unit 2101 receives input of aretrieval keyword from a user. When multiple retrieval keywords arereceived, the retrieval keyword input process unit 2101 connectsrespective character strings of the retrieval keywords. When consecutivecharacters of a retrieval keyword is equivalent to given consecutivecharacters, the retrieval keyword input process unit 2101 replaces theconsecutive characters with a non-standard character using thesubstitution table 640, and then fragments the retrieval keyword intosingle characters.

The retrieval keyword compressing unit 2102 compresses the retrievalkeyword input through the retrieval keyword input process unit 2101,using the Huffman tree 1810 generated by the Huffman tree generatingunit 1804 of the retrieval initializing unit 621. Using the appearancemap 510 set by the appearance map setting unit 1805, the appearance mapreading unit 2103, for each character of the retrieval keyword, reads astring of bits respectively corresponding to the forms files f0 to fn.Specifically, because each character data on the appearance maps 510 islinked to a row/column through the row/column corresponding table, theappearance map reading unit 2103 is able to read a string of bits foreach character data of the retrieval keyword matching the row/column.

The compressed forms file specifying unit 2104 calculates the logicalproduct of strings of bits respectively corresponding to the forms filesf0 to fn read from the appearance map 510 to specify a compressed formsfile in which all of the character data of the retrieval keyword arepresent, thus narrowing down compressed forms files. An example of anarrowing down process will be described.

FIG. 22 is a diagram of an example of narrowing down compressed formsfiles to a compressed forms file Fi. As depicted in FIG. 22, a retrievalkeyword is “

”, and the number of forms files is four, which means that filesincluding characters of the retrieval keyword are narrowed down to thefiles having file numbers i=0 to i=3. As depicted in FIG. 22, forexample, a bit string for a character “

” is [1100]. This bit string signifies that the forms files f0 and f1with file numbers 0 and 1 include the character “

” while the forms files f2 and f3 with file numbers 2 and 3 do notinclude the character “

”.

A narrowing down result depicted in FIG. 22 indicates the logicalproduct (AND) of bits for each file having a file number i. According tothis narrowing down result, only the forms file f1 having the filenumber 1 has, for each of the characters of the retrieval keyword, thebit “1” indicative of the presence of the character. Thus, all of thecharacters making up the retrieval keyword, i.e., “

”, “

”, “

”, and “

”, are present collectively only in the forms file f1, and are notpresent collectively in any of the other forms file f0, f2, and f3.Hence, a file to be opened as a file-to-be-retrieved is specified as thecompressed forms file Fi created by compressing the forms file fi. Thisprevents the opening/closing of unnecessary files to improve retrievalspeed.

Depicted in FIG. 21, the compressed forms file extracting unit 2105extracts, from among the compressed forms file group F, the forms fileFi specified by the compressed forms file specifying unit 2104. In theexample depicted in FIG. 22, the compressed forms file F1 having thefile number 1 is extracted.

The determining unit 2106 determines whether a retrieval keywordcompressed by the retrieval keyword compressing unit 2102 (hereinafter“compressed keyword”) is included in the compressed forms file Fiextracted by the compressed forms file extracting unit 2105.Specifically, this determination is made for each of compressed blockdata in the compressed forms file Fi.

When the result of the determination is “no matching”, it means that thecompressed forms file Fi does not include the retrieval keyword. Whenthe result of the determination is “matching”, it means that thecompressed forms file Fi includes the retrieval keyword. In the exampledepicted in FIG. 22, the compressed forms file F1 includes the retrievalkeyword “

”.

The block decompressing unit 2107 decompresses only the compressed blockdata of compressed forms file Fi that is determined to be “matching” bythe determining unit 2106. The determining unit 2106 and the blockdecompressing unit 2107 enable determination of the presence of theretrieval keyword in the compressed forms file Fi without decompression.If a determination result is “no matching”, the compressed forms file Fiis excluded from retrieval candidates before decompression of thecompressed forms file Fi, so that only the forms file(s) having a matchto the keyword is decompressed. When a decompressed forms file fiincludes consecutive characters/non-standard character data, the blockdecompressing unit 2107 substitutes the consecutivecharacters/non-standard character data with the original consecutivecharacters data, using the substitution table 640 decompressed by thedecompressing unit 1801.

The character string comparing unit 2108 compares a character string inblock data decompressed by the block decompressing unit 2107 with theretrieval keyword input through the retrieval keyword input process unit2101.

When a character string of the forms data gj matching the retrievalkeyword is present, the file data configuration specifying unit 2109specifies the page number j of the forms data gj and the file number iof a forms file fi to which the forms data gj belongs.

The retrieval candidate list display unit 2110 edits the page list data400, and extracts a file list on which the page number j of the formsdata gj and the file number i of the forms file fi to which the formsdata gj belongs is specified by the file data configuration specifyingunit 2109, from among file lists in the file configuration data 300 todisplay the extracted file list as a retrieval candidate list (e.g.,headword list) on the display 108 depicted in FIG. 1.

The retrieval candidate selecting unit 2111 receives a selection of aretrieval candidate, from among the retrieval candidate list displayedby the retrieval candidate list display unit 2110, by the user.

According to a character string no-matching check method in full textretrieval, although compressed/encoded data is not decompressed, aretrieval keyword is compressed to perform no-matching check.

In checking character strings of noncompressed data, comparison is madeaccording to each byte or each character. For compressed data, however,recognizing the boundary between characters is difficult, which makes itnecessary to shift bit by bit and make a comparison. Based onrecognition of this fact, the full text retrieval executing unit 624executes a no-matching check process on a compressed forms file, basedon byte-to-byte operation that the CPU 101 is well capable of.

FIG. 23 is a diagram of the no-matching check process carried out by thefull text retrieval executing unit 624. A retrieval keyword 2301 inputthrough the retrieval keyword input process unit 2102 depicted in FIG.21 is compressed by the retrieval keyword compressing unit 2102 into acompressed keyword 2302 of x bits, using the Huffman tree 1810, and isset in a register Ra.

Meanwhile, compressed block data 2312 in specified compressed forms file(compressed forms file) 2311 extracted by the compressed forms fileextracting unit 2105 is set in a register Rb, and is compared with thecompressed keyword 2302 set in the register Ra. Specifically, thecompressed block data 2312 shifted a given number of bytes is set in theregister Rb, and is compared sequentially with the compressed keyword2302.

Specifically, the XOR of the compressed keyword 2302 and the compressedblock data 2312 is calculated to output a comparison result 2320. A bitstring 2330 consisting of the final 8 bits of the comparison result 2320(meshed portion in FIG. 23) is then extracted, and is subjected tono-matching check.

FIG. 24 is a table of shift operation of shifting the compressed blockdata of FIG. 23. In this shift operation, the compressed block data isshifted at check intervals each corresponding to a compressed size(compressed keyword length) of the compressed keyword 2302. When thecompressed keyword length is 16 bits or longer, a bit length for checkdetermination is set to 8 bits. When the compressed keyword length is 11bits to 15 bits, the bit length for check determination is set to 3 bitsto 7 bits in adjustment of the final bits. When the compressed keywordlength is 1 bit to 10 bits, the no-matching check with respect to acompressed form is not carried out; however, the retrieval keyword 2301in a decompressed form is checked.

FIG. 25 is a diagram of a process of generating a preliminary checktable. In FIG. 25, the compressed keyword 2302 is set in the registerRa, in which “*” (last 8 bits) represent spaces that hold no bits of thecompressed keyword 2302. The compressed keyword 2302 in the register Rais shifted bit by bit to generate a shift table 2500. Since thecompressed keyword 2302 is composed of n bits, the generated shift table2500 is made up of shifted bit strings resulting from shifting rangingfrom 0 bit shift to x-8 bits shift.

The compressed keyword 2302 set in the register Ra and the shift table2500 are used in a preliminary check. Specifically, through an XORcalculation, an XOR table 2501 is generated. In each of the shifted bitstrings of the XOR table 2501, an 8-bit partial bit string ranging from17-th bit to 24-th bit that do not include “*” (meshed portion in FIG.25) is coupled with the number of shifts of the shifted bit stringcorresponding to partial bit string to generate a partial determinationtable 2502.

A preliminary check table 2503 for high-speed determination is thengenerated. The preliminary check table 2503 is generated by assigningthe number of shifts to an 8-bit address, with reference to the partialdetermination table 2502. When a bit string having a number of shiftsoverlapping another number of shifts appears, the number of shifts of“64” is assigned to the bit string, and the partial determination table2502 is referred to when this bit string is subjected to no-matchingcheck. The number of shifts of “−1” is assigned to a bit address notmatching any bit strings in the partial determination table 2502. Thepreliminary check table 2503 is compared with the bit string 2330 forno-matching check to perform no-matching check.

FIG. 26 is a diagram of an all bits no-matching check process. Asdepicted in FIG. 26, the current number of shifts is divided by 8 tocalculate the quotient and the remainder of the current number ofshifts. The quotient is added to the current pointer of the specifiedcompressed forms file 2311 to reacquire the compressed block data 2312corresponding to the pointer resulting from addition of the quotient,and the reacquired compressed block data 2312 is set in the register Rb.The set compressed block data 2312 is then shifted by the numberequivalent to the reminder.

The compressed keyword 2302 is set in the register Ra. In both registersRa and Rb, masking of bits not to be checked is turned off to comparethe register Ra with the register Rb. When both registers match in allbits thereof, the address of the matching bits is recorded.

FIG. 27 is a functional diagram of the numerical value retrievalexecuting unit 625 in the retrieval executing unit 622. The componentsidentical to those described with respect to FIG. 21 are denoted by thesame reference numerals, and description therefor is omitted.

As depicted in FIG. 27, the numerical value retrieval executing unit 625includes an acquiring unit 2701, a numerical value compressing unit2702, a detecting unit 2703, an intermediate numerical value groupdetermining unit 2704, an appearance map extracting unit 2705, anomitted map setting unit 2706, a lower limit/upper limit map generatingunit 2707, a specifying unit 2708, a compressed information retrievingunit 2709, a boundary condition determining unit 2710, and a designatingunit 2711.

The acquiring unit 2701 acquires a numerical value that defines theboundary of an arbitrary numerical value range. A numerical value rangeis a range that is specified by a numerical value and an operator eachdefining the boundary of the range. A numerical value defining theboundary includes a numerical value Nx defining the lower limit of thenumerical value range (lower limit numerical value), and a numericalvalue Ny defining the upper limit of the numerical value range (upperlimit numerical value). An operator defining the boundary represents aninequality, such as “≦”, “<”, “≧”, and “>”, serving as a boundarycondition by a lower limit numerical value or an upper limit numericalvalue.

Thus, when an arbitrary numerical value Z is given, the acquiring unit2701 can set the following numerical value ranges that a numerical valueN may take as a result of user input or initial setting of an operator.

-   -   Nx<Z    -   Nx≦Z    -   Nx>Z    -   Nx≧Z    -   Nx<Z<Ny    -   Nx≦Z<Ny    -   Nx<Z≦Ny    -   Nx≦Z≦Ny

The numerical value compressing unit 2702 compresses a numerical valueacquired by the acquiring unit 2701. Specifically, the numerical valuecompressing unit 2702 compresses the numerical value into compressedinformation including a compressed code for a feeder for numerical valuerecognition, a compressed code for a two-byte/one-byte bit, a compressedcode for a comma presence/absence bit, a compressed code for the numberof places, a compressed code for a numeral in each place, and acompressed code for a decimal point (when the numerical value includesthe decimal point). A numerical value in each compressed forms file Fiis compressed in this manner. The two-byte/one-byte bit, the commapresence/absence bit, and the respective compression codes therefor areall set to “0” (OFF).

The detecting unit 2703 detects the number of places and the headnumeral of a boundary-defining numerical value acquired by the acquiringunit 2701. For example, when the numerical value N is 12,345, the numberof places is “5” and the head number is “1”. When the numerical valueincludes a decimal point, the number of places following the decimalpoint is also counted. For example, when the numerical value N is12,345.67, the number of places is “7” and the head number is “1”. Whilethe uppermost place is regarded as the head place, a series ofupper-ranked places from the head may be regarded as the head place. Forexample, in the case of the numerical value N (N=12,345), the headnumeral may be regarded as “12”.

The intermediate numerical value group determining unit 2704 determineswhether an intermediate numerical value group is included in a numericalvalue range acquired by the acquiring unit 2701. An intermediatenumerical value group is a numerical value group that is present betweena numerical value group having the lower limit numerical value of thenumerical value range (hereinafter “lower limit numerical value group”)and a numerical value group having the upper limit numerical value ofthe numerical value range (hereinafter “upper limit numerical valuegroup”). If the lower limit numerical value group is different in thenumber of places from the upper limit numerical value group, thepresence of the intermediate numerical value group is concluded. If thenumber of places are the same but the head numerals are different, thepresence of the intermediate numerical value group is also concluded.

For example, when a numerical value range is “3,700 or more to 6,300 orless”, a numerical value group including numerical values with fourplaces and the head numeral of 3 are detected as a lower limit numericalvalue group, and a numerical value group including numerical values withfour places and the head numeral of 6 are detected as an upper limitnumerical value group. In this case, a numerical value group includingnumerical values with four places and the head numeral of 4 and anumerical value group including numerical values with four places andthe head numeral of 5 are intermediate numerical value groups within thenumerical value range.

Further, when a numerical value range is “3,700 to 16,300”, a numericalvalue group including numerical values with four places and the headnumeral of 3 are detected as a lower limit numerical value group, and anumerical value group including numerical values with five places andthe head numeral of 1 are detected as an upper limit numerical valuegroup. In this case, a numerical value group including numerical valueswith four places and the head numeral of 4 to a numerical value groupincluding numerical values with four places and the head numeral of 9are intermediate numerical value groups within the numerical valuerange.

When a numerical value range is “3,700 to 4,300”, a numerical valuegroup including numerical values with four places and the head numeralof 3 are detected as a lower limit numerical value group, and anumerical value group including numerical values with four places andthe head numeral of 4 are detected as an upper limit numerical valuegroup. In this case, there is no intermediate numerical value groupwithin the numerical value range.

Similarly, when a numerical value range is “3,700 to 3,900”, a numericalvalue group including numerical values with four places and the headnumeral of 3 are detected as a lower limit numerical value group, and anumerical value group including numerical values with four places andthe head numeral of 3 are detected as an upper limit numerical valuegroup, i.e., the lower limit numerical value group and the upper limitnumerical values group are the same numerical value group. In this caseas well, there is no intermediate numerical value group within thenumerical value range.

The appearance map extracting unit 2705 extracts appearance mapscorresponding to the number of places and the head numeral detected bythe detecting unit 2703, from among appearance maps for numerical valuegroups. For example, when the detecting unit 2703 detects the number ofplaces “5” and a head numeral “1”, the appearance map extracting unit2705 extracts an appearance map for a numerical value group includingnumerical values with five places and the head numeral of 1. When anintermediate numerical value group is present, an appearance map for theintermediate numerical value group is also extracted.

The omitted map setting unit 2706 sets an omitted map, based on theappearance map of the intermediate numerical value group. The omittedmap is set to calculate the logical product of the omitted map and theappearance map of the lower limit numerical value group and of theomitted map and the appearance map of the upper limit numerical valuegroup. Similar to the appearance map 503 of the numerical value group,the omitted map expresses the presence/absence of a numerical value in aforms file fi in the form of ON-bit and OFF-bit. The omitted map,therefore, indicates that a numerical value within the intermediatenumerical value group is present in the forms file fi corresponding toan ON-bit, and that a numerical value within the intermediate numericalvalue group is not present in the forms file fi corresponding to anOFF-bit.

The omitted map is, specifically, set by calculating the logical sum ofappearance maps of intermediate numerical value groups to create anintermediate result map and reversing bits in the intermediate resultmap. If only one appearance map of the intermediate numerical valuegroup is present, bits in this appearance map are reversed to set theomitted map. If the appearance map of the intermediate numerical valuegroup is not present, an omitted map having OFF-bits only is set.

The upper limit/lower limit map generating unit 2707 generates an upperlimit map and a lower limit map. The lower limit map is acquired bycalculating the logical product of the appearance map of the lower limitnumerical value group (lower limit numerical value group map) and theomitted map, and the upper limit map is acquired by calculating thelogical product of the appearance map of the upper limit numerical valuegroup (upper limit numerical value group map) and the omitted map. Thislogical product calculation creates the lower limit map as a mapindicative of the presence/absence of only the numerical values withinthe lower limit numerical value group, and creates the upper limit mapas a map indicative of the presence/absence of only the numerical valueswithin the upper limit numerical value group.

The specifying unit 2708 specifies a compressed file-to-be-retrievedhaving a numerical value within a numerical value group that satisfiesthe number of places and a head numeral detected by the detecting unit2703, among compressed files-to-be-retrieved. Specifically, thespecifying unit 2708 specifies the forms file fi corresponding to anON-bit among bits in the lower limit map to extract the compressed formsfile Fi from the compressed forms file group F, and, in the same manner,specifies the forms file fi corresponding to an ON-bit among bits in theupper limit map to extract the compressed forms file Fi from thecompressed forms file group F.

The compressed information retrieving unit 2709 retrieves from thecompressed forms file Fi specified by the specifying unit 2708,compressed information concerning an in-file numerical value. In thecompressed forms file Fi, in-file numerical values are compressed intocompressed information including a compression code for a feeder, acompression code for a two-byte/one-byte flag, a compression code for acomma flag, a compression code for the number of places, and acompression code for a numeral in each place. The compressed informationretrieving unit 2709 detects compressed information concerning anin-file numerical value (e.g., only the compression code for the feeder)to extract the detected compressed information.

The boundary condition determining unit 2710 compares compressedinformation of a boundary-defining numerical value compressed by thenumerical value compressing unit 2702 with compressed information of anin-file numerical value retrieved by the compressed informationretrieving unit 2709 to determine whether the in-file numerical valuesatisfies a boundary condition by the boundary-defining numerical value.The boundary condition is the condition that represents the sizerelation between the in-file numerical value and the boundary-definingnumerical value, such as the in-file numerical value being equal to orlarger than, being equal to or smaller than, being larger than, or beingsmaller than the boundary-defining numerical value.

For example, compressed codes for numerals of the numbers of places arecompared first to compare the sizes of the original pre-compressionnumerical values with each other. When the numbers of places areidentical, compression codes for the head numerals are compared witheach other to compare the sizes of the original numerical values witheach other. When the head numerals are identical, numerals in the placesfollowing the head place are compared sequentially with each other tocompare the sizes of the original numerical values with each other. Inthis way, whether the in-file numerical value satisfies the boundarycondition by the boundary-defining numerical value is determined.

Because two-byte/one-byte bits, comma presence/absence bits, andrespective compression codes therefore are all set to “0” (OFF) innumerical value compression, the two-byte/one-byte bits, commapresence/absence bits, and compression codes therefore are all set to“0” (OFF) in compressed information when compressed information of thein-file numerical value is compared with compressed information of theboundary-defining numerical value. This allows execution of numericalvalue retrieval without considering a difference in two-byte/one-byteand/or the presence/absence of a comma.

The designating unit 2711 designates the compressed file-to-be-retrievedFi specified by the specifying unit 2708 to be a file having a numericalvalue within the numerical value range, based on a determination resultgiven by the boundary condition determining unit 2710. Specifically,when the in-file numerical value satisfies the boundary condition by theboundary-defining numerical value, the designating unit 2711 designatesthe compressed file-to-be-retrieved Fi specified by the specifying unit2708 to be the file having the numerical value within the numericalvalue range. In this designating process, a lower limit comparisonresult map and an upper limit comparison result map are used, which mapsare expressed by bit strings corresponding to forms files, as theappearance maps are. All bits in the maps are set OFF in the initialsetting.

In the compressed forms file Fi, when the in-file numerical valuesatisfies the boundary condition by the lower limit numerical value, abit in the lower limit comparison result map that corresponds to thecompressed forms file Fi is set ON. Likewise, when the in-file numericalvalue satisfies the boundary condition by the upper limit numericalvalue, a bit in the upper limit comparison result map that correspondsto the compressed forms file Fi is set ON.

The designating unit 2711 then calculates the logical sum of the finallyacquired lower limit comparison result map, the upper limit comparisonresult map, and an intermediate result map, if it is present, todesignate the compressed forms file Fi having the numerical value withinthe numerical value range.

When the designating unit 2711 determines the compressed forms file Fihaving the numerical value within the numerical value range, the fileconfiguration data specifying unit 2109 specifies the page number j offorms data gj having the in-file numerical value satisfying the boundarycondition by the boundary-defining numerical value, and the file numberi of the forms file fi to which the forms data gj belongs.

An exemplary case will be described, in which the lower limit numericalvalue and the upper limit numerical value that define a numerical valuerange have the same number of places and different numerals at the headplaces. FIGS. 28A to 28D are explanatory diagrams of examples of sizecomparison in a numerical value range. In the examples, a numericalvalue range “3,700 to 6,300 yen” is given and a compressed forms file Fihaving an amount of money (numerical value) within the range specifiedby the numerical value range is retrieved. Numerical value informationof the lower limit numerical value “3,700 yen” and that of the upperlimit numerical value “6,300 yen” are both compressed by the compressingprocess of FIG. 16C.

As depicted in FIG. 28A, with respect to the numerical value range“3,700 to 6,300 yen”, an appearance map of an intermediate numericalvalue group is extracted first. Specifically, a four-place/head numeral4 map M44 and a four-place/head numeral 5 map M45 are extracted asappearance maps of the intermediate numerical value group, the maps M44and M45 being present between a four-place/head numeral 3 map M43equivalent to an appearance map of a lower limit numerical value groupand a four-place/head numeral 6 map M46 equivalent to an appearance mapof an upper limit numerical value group.

The four-place/head numeral 3 map M43 represents the presence/absence ofa forms file fi having a numerical value with four places and the headnumeral of 3. The four-place/head numeral 4 map M44 represents thepresence/absence of a forms file fi having a numerical value with fourplaces and the head numeral of 4. The four-place/head numeral 5 map M45represents the presence/absence of a forms file fi having a numericalvalue with four places and the head numeral of 5. The four-place/headnumeral 6 map M46 represents the presence/absence of a forms file fihaving a numerical value with four places and the head numeral of 6.

The four-place/head numeral 3 map M43 and the four-place/head numeral 6map M46 are the appearance maps that are used for size comparison. Thefour-place/head numeral 4 map M44 and the four-place/head numeral 5 mapM45 are subjected to logical sum calculation to create an intermediateresult map M01, which represents the presence/absence of a forms file fihaving numerical values 4000 to 5999. Bits on this intermediate resultmap M01 are reversed to acquire an omitted map M02.

As depicted in FIG. 28B, the logical product of the four-place/headnumeral 3 map M43 and the omitted map M02 of FIG. 28A is calculated toacquire a lower limit map M03. Calculating the logical product of thefour-place/head numeral 3 map M43 and the omitted map M02 eliminates aforms file having a numerical value within the intermediate numericalvalue group.

A compressed forms file Fi with an ON-bit is extracted from the lowerlimit map M03. The extracted compressed forms file Fi is then searchedfrom the head thereof to find a compression code “1011” for a feeder(“x′B′” in FIG. 28B). When the compression code “1011” for the feeder isfound, compressed information 2801 having the compression code “1011”for the feeder at its head is read out. When a two-byte/one-byte bit anda comma presence/absence bit in the compressed information 2801 arerespectively “1”, both bits are turned to “0” in masking conversion. Thecompressed information resulting from the masking conversion is referredto as compressed information to-be-compared 2810.

The compressed information to-be-compared 2810 acquired by compressingnumerical value information “3,300 yen” in the compressed forms file Fiis then compared with lower limit compressed information 2802 acquiredby compressing lower limit numerical value information “3,700 yen”.First, compression codes for feeders, for the number of places, and forthe head numerals of the compressed information to-be-compared 2810 andthe lower limit compressed information 2802 are compared with each otherfor matching. If, at this stage, any one type of compressed codes do notmatch, the next feeder in the compressed forms file Fi is retrieved.

When the compression codes for the feeders match, it indicates that thecompressed information to-be-compared 2810 and the lower limitcompressed information 2802 are the same type of numerical valueinformation. When the numbers of places match, it indicates that thecompressed information to-be-compared 2810 is at least a compressed formof a numerical value of a four-digit number. When the head numeralsmatch, it indicates that the compressed information to-be-compared 2810is at least a compressed form of a numerical value with the head numeralof “3”. When all of the compression codes for the feeders, the number ofplaces, and the head numerals match, therefore, compression codes fornumerals in the same place are compared in size.

In this example, compression codes for the second numerals are comparedrevealing that the lower limit numerical value information “3,700 yen”is larger than the numerical value information “3,300 yen” in thecompressed information to-be-compared 2810. In this case, the bitcorresponding to the compressed forms file Fi remains “0” in the lowerlimit comparison result map M04. Subsequently, the next feeder in thecompressed forms file Fi is retrieved. When numerical value informationequal to or larger than the lower limit numerical value information“3,700 yen” is present, the bit corresponding to the compressed formsfile Fi is turned to “1” in the lower limit comparison result map M04.

This comparison process is carried out on each of the compressed formsfiles F0 to Fn for which a bit is ON in the lower limit map M03 toacquire the lower limit comparison result map M04. In this manner, thecompressed forms file Fi having a numerical value with four places andthe head numeral of “3” is extracted from the lower limit map M03. Thisenables the forms file fi to be retrieved in its compressed form.

As depicted in FIG. 28C, the logical product of the four-place/headnumeral 6 map M46 and the omitted map M02 of FIG. 28A is calculated toacquire an upper limit map M05. Calculating the logical product of thefour-place/head numeral 3 map M43 and the omitted map M02 eliminates aforms file having a numerical value within the intermediate numericalvalue group.

A compressed forms file Fi with an ON-bit is extracted from the upperlimit map M05. The extracted compressed forms file Fi is then searchedfrom the head thereof to find a compression code “1011” for a feeder(“x′B′” in FIG. 28C). When the compression code “1011” for the feeder isfound, compressed information 2803 having the compression code “1011”for the feeder at its head is read out. When a two-byte/one-byte bit anda comma presence/absence bit in the compressed information 2803 arerespectively “1”, both bits are turned to “0” in masking conversion. Thecompressed information resulting from the masking conversion is referredto as compressed information to-be-compared 2830.

The compressed information to-be-compared 2830 acquired by compressingnumerical value information “6,200 yen” in the compressed forms file Fiis then compared with upper limit compressed information 2804 acquiredby compressing upper limit numerical value information “6,300 yen”.First, compression codes for feeders, for the number of places, and forthe head numerals of the compressed information to-be-compared 2830 andthe upper limit compressed information 2804 are compared with each otherfor matching. If, at this stage, any one type of compressed codes do notmatch, the next feeder in the compressed forms file Fi is retrieved.

When the compression codes for the feeders match, it indicates that thecompressed information to-be-compared 2830 and the upper limitcompressed information 2804 are the same type of numerical valueinformation. When the numbers of places match, it indicates that thecompressed information to-be-compared 2830 is at least a compressed formof a numerical value of a four-digit number. When the head numeralsmatch, it indicates that the compressed information to-be-compared 2830is at least a compressed form of a numerical value with the head numeralof “6”. When all of the compression codes for the feeders, the number ofplaces, and the head numerals match, therefore, compression codes fornumerals in the same place are compared in size.

In this example, compression codes for the second numerals are comparedrevealing that the upper limit numerical value information “6,300 yen”is larger than the numerical value information “6,200 yen” in thecompressed information to-be-compared 2830. In this case, the bitcorresponding to the compressed forms file Fi is changed to “1” in theupper limit comparison result map M06.

This comparison process is carried out on each of the compressed formsfiles Fi for which a bit is ON in the upper limit map M05 to acquire theupper limit comparison result map M06. In this manner, the compressedforms file Fi having a numerical value with four places and the headnumeral of “6” is extracted from the upper limit map M05. This enablesthe forms file fi to be retrieved in its compressed form.

As depicted in FIG. 28D, the logical sum of the lower limit comparisonresult map M04, the intermediate result map M01, and the upper limitcomparison result map M06 is calculated to acquire a comprehensiveresult map M07. Hence, a forms file fi having numerical valueinformation within the numerical value range “3,700 yen to 6,300 yen”can be specified remaining in a compressed form.

In the examples depicted in FIGS. 28A to 28D, the lower limit numericalvalue and the upper limit numerical value that define the numericalvalue range have the same number of places and different numerals in thehead places. The above size comparison, however, may also be carried outeven when the number of places of the upper limit numerical value islarger (or the number of places of the lower limit numerical value issmaller). For example, when a numerical value range is “3,700 yen to64,000 yen”, four-place/head numeral 4 map to four-place/head numeral 9map and five-place/head numeral 1 map to five-place/head numeral 5 mapare extracted as appearance maps of an intermediate numerical valuegroup.

When a numerical value range is “3,700 yen to 3,900 yen”, “3,700 yen to4,500 yen”, etc., an intermediate numerical value group is not present,so that the intermediate result map M01 is not present. In this case,therefore, all bits in the omitted map M02 are set to OFF. Because ofthe absence of the intermediate result map M01, the comprehensive resultmap M07 is acquired by calculating the logical sum of the lower limitcomparison result map M04 and the upper limit comparison result map M06.

FIG. 29 is a functional diagram of the retrieval result display unit 623depicted in FIG. 6. As depicted in FIG. 29, the retrieval result displayunit 623 includes a reading unit 2901, a file decompressing unit 2902,and a file display unit 2903.

The file decompressing unit 2902 reads from a compressed forms file Fiin the compressed forms file group F, item data, which is a retrievalcandidate selected by the retrieval candidate selecting unit 2111. Thefile decompressing unit 2902 decompresses the item data read out by thereading unit 2901, using the Huffman tree 1801. The file display unit2903 displays the item data decompressed by the file decompressing unit2902 as a retrieval result.

FIG. 30 is a flowchart of an information retrieval process by theinformation retrieval apparatus 600 according to the embodiment of thepresent invention. As depicted in FIG. 30, the appearance frequencymanagement data generating unit 612 executes an appearance frequencymanagement data generating process (step S3001).

The compressing/encoding unit 613 then executes a compressing/encodingprocess (step S3002). Subsequently, the retrieval initializing unit 621executes a retrieval initializing process (step S3003). The retrievalexecuting unit 622 then executes a retrieval process (step S3004).

Finally, the retrieval result display unit 623 executes a retrievalresult display process (step S3005). In the retrieval result displayprocess, a retrieval candidate (item data) selected from a retrievalcandidate list is read out from the compressed forms file Fi, and isdecompressed using the Huffman tree 1810 to display the full text of theitem data as a retrieval result.

FIG. 31 is a flowchart of the appearance frequency management datagenerating process (step S3001) of FIG. 30. As depicted in FIG. 31, aninitializing process is executed (step S3101). Specifically, a totalingarea corresponding to the row/column code of 8-bit/16-bit numericalvalue/character data, consecutive characters data, and binary data isestablished, and segments, etc., of the appearance frequency and theappearance map are initialized. The code for numerical value/characterdata is set, and various counters are initialized.

A numerical value/character appearance frequency totaling process isthen executed (step S3102). A detailed procedure of the numericalvalue/character appearance frequency totaling process will be describedlater. Following the numerical value/character appearance frequencytotaling process, an area for the appearance frequency management data500 is established and initialized (step S3103), and the character codeand appearance frequency of 8-bit/16-bit numerical value/character data,consecutive characters data, and binary data is set (step S3104).

Respective segments of the appearance map are linked (step S3105), andconsecutive characters data in the consecutive characters area aresorted in descending order of appearance frequency (step S3106) toselect 256 types of consecutive characters data. This reduces the volumeof consecutive characters data.

Subsequently, a consecutive characters/non-standard charactersubstitution process is carried out, and the substitution table 640 isgenerated (step S3107). Specifically, consecutive characters data issubstituted with non-standard character data in descending order ofappearance frequency to generate consecutive characters/non-standardcharacter data and the substitution table 640.

Consecutive charters data with a low appearance frequency, that is,consecutive characters data not substituted with non-standard characterdata, is fragmented into single character data, which are allocated tothe corresponding areas in a revision process (step S3108).Specifically, consecutive charters data with a low appearance frequencyis divided into phonogramic data, the frequency of which is subject toaddition and the appearance map of which is subject to logical ORcalculation.

Subsequently, numerical value/character data is sorted in descendingorder of appearance frequency (step S3109), and numericalvalue/character data having zero frequency is cut out, and thenconsecutive characters/non-standard character data and binary data iscombined together (step S3110). The appearance frequency management data500 resulting from the joining is output to a file (step S3111), afterwhich the procedure proceeds to step S3002.

FIG. 32A is a (first half) flowchart of the numerical value/characterappearance frequency totaling process (step S3102). As depicted in FIG.32A, the head forms file f0 is opened first (step S3201).

Data is extracted sequentially from the opened forms file. Whenextracted data is binary data (step S3202: YES), the appearancefrequency of the binary data is added, and the bit corresponding to theopened file on the appearance map of the binary data is set to “1”, andthen a byte counter adds an additional count (step S3203), after whichthe procedure proceeds to step S3211 of FIG. 32B.

When extracted data is not binary data at step S3202 (step S3202: NO),whether the extracted data is a numerical value is determined (stepS3204). For example, the extracted data of a numerical string consistingof numerals is determined to be a numerical data. The extracted data ofa numerical string including a comma “,” and a decimal point “.” inaddition to numerals is also determined to be a numerical value.

When the extracted data is a numerical value (step S3204: YES), theappearance frequency of the numerical value is added, and the bitcorresponding to the opened file on the appearance map of the numericalvalue is set to “1”, and then the byte counter adds an additional count(step S3205), after which the procedure proceeds to step S3211 of FIG.32B.

When the extracted data is not a numerical value at step S3204 (stepS3204: NO), whether the extracted data is consecutive characters data isdetermined (step S3206). When the extracted data is consecutivecharacters data (step S3206: YES), the appearance frequency of theconsecutive characters data is added, and the bit corresponding to theopened file on the appearance map of the consecutive characters data isset to “1”, and then the byte counter adds an additional count (stepS3207), after which the procedure proceeds to step S3211 of FIG. 32B.

When the extracted data is not consecutive character data at step S3206(step S3206: NO), whether the extracted data is kanji data is determined(step S3208). When the extracted data is not kanji data (step S3208:NO), the extracted data is phonogramic data. Accordingly, the appearancefrequency of the phonogramic data is added, and the bit corresponding tothe opened file on the appearance map of the phonogramic data is set to“1”, and then the byte counter adds an additional count (step S3209),after which the procedure proceeds to step S3211 of FIG. 32B.

When the extracted data is kanji data at step S3208 (step S3208: YES),the appearance frequency of the kanji data is added, and the bitcorresponding to the opened file on the appearance map of the kanji datais set to “1”, and then the byte counter adds an additional count (stepS3210), after which the procedure proceeds to step S3211 of FIG. 32B.

FIG. 32B is a (second half) flowchart of the numerical value/characterappearance frequency totaling process (step S3102). As depicted in FIG.32B, a segment counter for segments of the appearance map adds anadditional count (step S3211), and whether a segment is finished, thatis, whether the totaling process with respect to the segments isfinished is determined (step S3212). When the totaling process withrespect to the segments is finished (step S3212: YES), the segment ofthe appearance map is output additionally to the file, and the segmentcounter is reset (step S3213), after which the procedure proceeds tostep S3214.

When the totaling process on the segments is not finished (step S3212:NO) or after execution of step S3213, whether a block is finished, e.g.,whether the total number of numerical value/characters reaches 4,000characters is determined (step S3214).

When the block is finished (step S3214: YES), block information made upof the file number i of a forms file fi having the block data, and theblock number m, offset, number of characters, and length of the blockdata is generated, and is output additionally to the file, and the bytecounter is reset (step S3215), after which the procedure proceeds tostep S3216.

When the block is not finished (step S3214: NO) or after execution ofstep S3215, whether the file is finished, that is, whether the totalingprocess with respect to the currently opened forms file fi is finishedis determined (step S3216). When the totaling process with respect tothe currently opened forms file fi is not finished (step S3216: NO), theprocedure returns to step S3202 of FIG. 32A, at which the next data isextracted, and the type of the extracted data is specified to performthe totaling process (steps S3202 to S3210).

When the totaling process on the currently opened forms file is over atstep S3216 (step S3216: YES), whether the totaling process comes to anend is determined, and the end of the totaling process leads to closingof the currently opened forms file Fi (step S3217). Subsequently,whether the totaling process on each of the forms files F0 to Fn hasbeen completed is determined (step S3218).

When the totaling process on each of the forms files F0 to Fn has notbeen completed (step S3218: NO), a forms file fi having the next filenumber i (i=i+1) is opened (step S3219). The procedure then returns tostep S3202 of FIG. 32A, at which the next data is extracted, and thetype of the extracted data is specified to perform the totaling process(steps S3202 to S3210).

When the totaling process on each of the forms files F0 to Fn has beencompleted as determined at step S3218 (step S3218: YES), the segment ofthe appearance map 510 is output additionally to the file (step S3220),after which the procedure proceeds to step S3203 to end a series ofprocesses.

FIG. 33 is a flowchart of the compressing/encoding process (step S3002)of FIG. 30. As depicted in FIG. 33, the appearance frequencies of anumeral, a decimal point, and a feeder (hereinafter “numeral, etc.”) arerevised (step S3301), and the appearance frequency of other characterdata is also revised (step S3302).

Subsequently, numerical value/character data in the mixture area 812 aresorted in the order of appearance frequency (step S3303). Numericalvalue/character data with a low appearance frequency is fragmented into8-bit data, of which the appearance frequency is added to the appearancefrequency of binary data corresponding to the 8-bit data (step S3304).Numerical value/character data, consecutive characters/non-standarddata, and binary data in the mixture area 812 are linked, and sorted inthe order of appearance frequency (step S3305).

Subsequently, the occurrence probability of each type of sortednumerical value/character data is calculated based on the revisedappearance frequency (step S3306). Based on the calculated occurrenceprobability, a Huffman tree common to 8-bit/16-bit numericalvalue/character data is generated (step S3307).

A compressing process of compressing each of the forms file is thencarried out (step S3308). A specific procedure of this compressingprocess will be described later. The appearance frequency managementdata 500 is encoded (step S3309). Specifically, an encoding area of theappearance frequency management data 500 (area for numericalvalue/character data and appearance frequency) is encoded throughexclusive-OR (XOR), using a master key.

The substitution table 640 is then encoded (step S3310). Specifically,an encoding area of the substitution table 640 is encoded throughexclusive-OR (XOR), using a master key. Subsequently, the procedureproceeds to the retrieval initializing process (step S3003) to end aseries of processes.

FIG. 34 is a flowchart of the compressing process of step S3308 of FIG.33. First, the file number i is set to 0 (step S3401), and the formsfile i is divided into blocks of, for example, 4,000 characters (stepS3402). Subsequently, data in the forms file i are read in sequentially,and whether read data is a feeder is determined (step S3403).

When the read data is determined to be the feeder (step S3403: YES), aseries of numerals following the feeder are read in as a numerical value(step S3404), and the two-byte or one-byte and the number of places ofthe numerical value are detected (step S3405). The numerical value isthen compressed using the Huffman tree (step S3406), after which theprocedure proceeds to step S3408.

When the read data is determined to be not the feeder (step S3403: NO),the data is other character data, which is then compressed using theHuffman tree (step S3407), after which the procedure proceeds to stepS3408.

At step S3408, whether the compression process in the current block isover is determined (step S3408). When the compression process is notfinished (step S3408: NO), the procedure returns to step S3403, at whichthe next data is read in. When the compression process is over (stepS3408: YES), whether an unprocessed block is present is determined (stepS3409).

When an unprocessed block is present (step S3409: YES), the unprocessedblock is read in (step S3410), and the procedure returns to step S3403,at which data is read in. When an unprocessed block is not present (stepS3409: NO), the file number i is increased by 1 (step S3411), andwhether i>n is satisfied is determined (step S3412).

When i>n is not satisfied (step S3412: NO), the procedure returns tostep S3402, at which the next forms file i is divided into blocks. Wheni>n is satisfied (step S3412: YES), the procedure proceeds to step S3309of FIG. 33. Hence, a series of processes making up the compressingprocess are ended.

FIG. 35 is a flowchart of the retrieval initializing process (stepS3303) of FIG. 30.

As depicted in FIG. 35, the start of the retrieval initializing processis waited for (step S3501: NO). When the retrieval initializing processstarts (step S3501: YES), the encoded appearance frequency managementdata 650 encode by the compressing/encoding process is decoded (stepS3502). Specifically, the encoding area of the encoded appearancefrequency management data 650 (area for numerical value/character dataand appearance frequency) is decoded through exclusive-OR (XOR), usingthe master key used in the encoding process.

The encoded substitution table 660 is decoded (step S3503).Specifically, the encoding area of the encoded substitution table 660 isdecoded through exclusive-OR (XOR), using the master key used in theencoding process.

Processes identical to the processes at steps S3401 to S3405 in thecompressing/encoding process are then carried out. Specifically,numerical value/character data is sorted in descending order ofappearance frequency (step S3504), and numerical value/character datahaving a low appearance frequency is fragmented into 8-bit data, ofwhich the appearance frequency is added to the appearance frequency ofbinary data corresponding to the 8-bit data (step S3505).

Numerical value/character data, consecutive characters data, and binarydata are linked, and sorted in descending order of appearance frequency(step S3506). Subsequently, the occurrence probability of each type ofsorted numerical value/character data is calculated based on theappearance frequency (step S3507). Based on the calculated occurrenceprobability, a Huffman tree common to 8-bit/16-bit numericalvalue/character data is generated (step S3508).

Subsequently, a process of setting the appearance map 510 is carried out(step S3509). Specifically, an area for the first row/columncorresponding table and the second row/column corresponding table isestablished, the appearance frequency of each of character data is setto the first row/column corresponding table, the appearance frequency ofeach of numerical value data is set to the second row/columncorresponding table, the appearance map of the decoded appearancefrequency management data 500 is expanded on a memory, and theappearance map is linked to the first row/column corresponding table andto the second row/column corresponding table. Subsequently, theprocedure proceeds to the retrieval process (step S3004) to end a seriesof processes.

FIG. 36 is a flowchart of the retrieval process (step S3004) of FIG. 30.As depicted in FIG. 36, following the retrieval initializing process(step S3003), a retrieval mode screen is called up (step S3601), andselection of a numerical value retrieval mode or of a characterretrieval mode is waited for (step S3602).

When the numerical value retrieval mode is selected (step S3602: YES),the procedure proceeds to step S4001 of FIG. 40. When the characterretrieval mode is selected (step S3602: NO), an input retrieval keywordis received (step S3603).

When the retrieval keyword does not consist of multiple retrievalkeywords (step S3604: NO), the process proceeds to step S3606. When theretrieval keyword consists of multiple keywords (step S3604: YES),character strings of the keywords are connected (step S3605), and theprocess proceeds to step S3606.

At step S3606, when consecutive characters data is not present in theretrieval keyword (step S3606: NO), the process proceeds to step S3608.When consecutive characters data is present in the retrieval keyword(step S3606: YES), the consecutive characters data is substituted withnon-standard character data consisting of two characters, using thesubstitution table 640 (step S3607), and the process proceeds to stepS3608.

At step S3608, the retrieval keyword is fragmented into single characterdata, and the bit string for each character data indicative of thepresence/absence of the character with respect to each forms file isread from the appearance map (step S3608). Subsequently, the logicalproduct of the bit strings indicative of the presence/absence of thecharacter is calculated to specify (i.e., narrow down files to) acompressed forms file (step S3609). The retrieval keyword is compressedusing the Huffman tree generated by the retrieval initializing processat step S3003 (step S3610).

A preliminary check table generating process (step S3611) is thenexecuted. A detailed procedure of the preliminary check table generatingprocess will be described later with reference to FIG. 37. Following thegeneration of the preliminary check table, a file counter is initialized(step S3612).

Subsequently, the compressed forms file specified at step S3609(hereinafter “specified compressed forms file”) is opened (step S3613).Each compressed block data of the opened specified compressed forms fileis compared with the compressed keyword in execution of a no-matchingdetermining process (step S3614). This no-matching determining processwill be described later with reference to FIG. 38.

In the no-matching determining process, when each of the compressedblock data has been determined to not match the compressed keyword (stepS3615: YES), the procedure proceeds to step S3618. When any one ofcompressed block data is determined to match the keyword (step 3615:NO), the compressed block data determined to match is decompressed usingthe Huffman tree (step S3616). The decompressed block data is thencompared with the retrieval keyword, and the file number and the anchorof item data matching the retrieval keyword are recorded (step S3617),then the process proceeds to step S3618.

Subsequently, the opened specified compressed forms file is closed (stepS3618), and the file counter is updated (step S3619). When the presenceof an unprocessed specified compressed forms file is determined as aresult of file counter updating (step S3620: YES), the process proceedsto step S3613, at which the next specified compressed forms file isopened.

When no unprocessed specified compressed forms file are determined to bepresent (step S3620: NO), the retrieval candidate list is displayed(step S3621), and an input of retrieval candidate selection from a useris waited for (step S3622). The process proceeds to the retrieval resultdisplay process (step S3005), ending a series of processes.

In this manner, even if the contents are composed of multiple formsfiles, the forms files can be processed in common in the form of asingle piece of compressed information (appearance frequency managementdata 500).

The data contents of a forms file of a large size is blocked accordingto the number of character data. This allows application of the Huffmancompression technique to a file-to-be-retrieved having a mixture of8-bit code character data, 16-bit code character data, and 32-bit codecharacter data.

Blocking is carried out not according to file size (volume) butaccording to the number of character data, and when the appearancefrequency of each type of character data in a forms file is summed, thetype of the character data (8-bit code, 16-bit code, and 32-bit code) isdetermined to total the appearance frequency.

Eight-bit code character data having a high appearance frequency, suchas English character data in an English-Japanese dictionary, issubstituted with 16-bit code character data, such as “Ox′FF**”, and issubjected to Huffman compression. This distinguishes 8-bit codecharacter data with a high appearance frequency from 8-bit codecharacter data with a low appearance frequency to enable efficientcompression.

Noncharacter data, such as a pointer, takes a random value, and is,therefore, replaced with an 8-bit code data. For reducing the size ofthe Huffman tree, 16-bit code character data having a low appearancefrequency is divided into 8-bit code character data. This enablesefficient compression.

The appearance frequency management data 500, from which the Huffmantree for compression is generated, is encoded entirely or partially.Contents or the Huffman tree for compressing the contents is notdirectly encoded but the original data from which the Huffman tree isgenerated is encoded. This improves security.

Based on the appearance frequency management data 500, the speed of fulltext retrieval is increased. Consecutive characters data consisting oftwo characters with a high appearance frequency included in consecutivephonogramic data is substituted with non-standard character data, andthen contents are compressed. This improves the rate of compression.

Consecutive charters data decreases the number of files to open andclose, reducing a character string comparison area to speed up full textretrieval. In full text retrieval, decompressed non-standard characterdata is directly compared with a retrieval keyword in character stringcomparison to further increase retrieval speed.

FIG. 37 is a flowchart of a preliminary check table generating process.As depicted in FIG. 37, the total number of shifts of the compressedkeyword 2302 is calculated first (step S3701). Specifically, the lengthof bits not holding the compressed keyword 2302 (“*” of FIG. 25) iscalculated as the total number of shifts, from the length of thecompressed keyword and the length of bits in the register Ra.

Subsequently, a check interval (number of bytes) is calculated referringto the table of shift operation of FIG. 24 (step S3702). The compressedkeyword 2302 is then shifted by the total number of shifts on abit-to-bit basis to make the shift table 2500 (step S3703). The bitstrings on the shift table 2500 and the compressed keyword 2302 aresubject to XOR calculation to make the XOR table 2501 (step S3704).

The partial determination table 2502 is then made from the XOR table2501 and the numbers of shifts of the bit strings making up the XORtable 2501 (step S3705). The preliminary check table 2503 is made usingthe partial determination table 2502 (step S3706), after which theprocess proceeds to step S3612.

FIG. 38 is a flowchart of a process of determining no matching ofcompressed block data with respect to a compressed keyword. As depictedin FIG. 38, the compressed keyword 2302 is set in the register Ra (stepS3801).

Subsequently, a check interval (number of bytes) at which the compressedblock data 2312 is shifted is set (step S3802), and a pointer of thespecified compressed forms file 2311 is initialized (step S3803).Following the current pointer, the compressed block data 2312 is set inthe register Rb (step S3804). The exclusive-OR of the register Ra andthe register Rb is then calculated (step S3805) to extract the bitstring 2330 consisting of the last 8 bits (step S3806).

Subsequently, the extracted bit string 2330 of the last 8 bits ischecked against the preliminary check table 2503 to detect the number ofshifts of a bit string matching the bit string 2330 of the last 8 bitsamong bit strings in the preliminary check table 2503. Whether thedetected number of shifts is “−1”, that is, whether the compressed blockdata 2312 does not match the compressed keyword 2302 is determined (stepS3807).

When the number of shifts is “−1” (step S3807: YES), a pointer of thespecified compressed forms file 2311 is added at the check interval(step S3808), and whether the compressed block data 2312 is not presentis determined (step S3809). When the compressed block data 2312 ispresent (step S3809: NO), the procedure returns to step S3804. When thecompressed block data 2312 is not present (step S3809: YES), theprocedure proceeds to step S3615. Steps S3804 to S3809: NO form a loop,which enables faster check to determine no matching; thereby, enablingimproved retrieval speed.

When the number of shifts is not “−1” at step S3807 (step S3807: NO),but is 0 to 63 (0 to 63 at step S3810), which means partial matching,the number of shifts is acquired (step S3811) to execute an all bitsno-matching check process (step S3812), which will be described later.Subsequently, the procedure proceeds to step S3808.

When the number of shifts is 64 at step S3810 (step S3810: 64), whichmeans overlapping partial matching, a pointer of the partialdetermination table 2502 is initialized (step S3813), and the XOR resultof the partial determination table 2502 that corresponds to the currentpointer is acquired (step S3814). Whether the bit string correspondingto the number of shifts of 64 matches the XOR result of the partialdetermination table 2502 that corresponds to the current pointer is thendetermined (step S3815). When no matching results (step S3815: NO), theprocess proceeds to step S3818.

When matching results (step S3815: YES), the number of shiftscorresponding to the XOR result is acquired from the partialdetermination table 2502 (step S3816) to execute the all bitsno-matching check process (step S3817). This all bits no-matching checkprocess (step S3817) is equivalent to the all bits no-matching checkprocess at step S3812, and will be described later.

Following the all bits no-matching check process (step S3817), pointersof the partial determination table 2502 are summed (step S3818). Whenthe current pointer of the partial determination table 2502 is not thefinal pointer (step S3819: NO), the process returns to step S3814. Whenthe current pointer of the partial determination table 2502 is the finalpointer (step S3819: YES), the process returns to step S3808.

FIG. 39 is a flowchart of the all bits no-matching check process (stepS3812 and step S3817). As depicted in FIG. 39, the number of shifts isdivided by 8 to acquire the quotient and the remainder thereof (stepS3901).

The quotient is then added to the current pointer of the specifiedcompressed forms file 2311 (step S3902), and the compressed block data2312 is set in the register Rb (step S3903). The set compressed blockdata 2312 is shifted by the number of shifts equivalent to the remainder(step S3904).

Subsequently, the compressed keyword 2302 is set in the register Ra(step S3905), and masking of bits not to be subjected to check is turnedoff in both registers Ra and Rb (step S3906). When both registers matchin all bits thereof (step S3907: YES), the address represented by thematching bits is recorded (step S3908), after which the procedureproceeds to step S3808 (or to step S3817). When all of the bits do notmatch (step S3907: NO), the process proceeds to step S3808 (or to stepS3817).

In this manner, the method of no-matching check based on thebyte-to-byte operation that the CPU 101 of the computer is well capableof is carried out in no-matching check with respect to the specifiedcompressed forms file 2311. For preliminary check per bit, the XOR ofthe compressed keyword 2302 made by compressing the input retrievalkeyword 2301 and the shift table 2500 representing the set of dataresulting from bit-by-bit shifting of the compressed keyword 2302 iscalculated, and no-matching check is carried out based on the result ofthe XOR calculation. A check interval for comparison between thecompressed keyword and the specified compressed forms file 2311 islengthened according to the length of the compressed keyword to speed upno-matching check.

FIG. 40 is a flowchart of a numerical value retrieval executing processin a numerical value retrieval mode according to the embodiment of thepresent invention.

Following step S3602: YES of FIG. 36, the acquiring unit 2701 acquires anumerical value range (step S4001). Subsequently, the detecting unit2703 detects the number of places and the head numeral of a numericalvalue (lower limit numerical value or upper limit numerical value)defining the boundary of the numerical value range (step S4002). Thenumerical value compressing unit 2702 then compresses a lower limitnumerical value and an upper limit numerical value (step S4003).

Subsequently, the appearance map extracting unit 2705 extractsappearance maps of numerical groups ranging from a lower limit numericalvalue group to an upper limit numerical value group, from the appearancemap 501 (step S4004). The intermediate numerical value group determiningunit 2704 then determines whether an intermediate numerical value groupis present (step S4005). When the presence of the intermediate numericalvalue group is determined (step S4005: YES), the omitted map settingunit 2706 calculates the logical sum of appearance maps of intermediatenumerical value groups to generate an intermediate result map (stepS4006), and reverses all bits in the intermediate result map to convertit into an omitted map (step S4007).

When the absence of the intermediate numerical value group is determined(step S4005: NO), the omitted map is initialized (step S4008).Specifically, bits strings corresponding to the forms files f0 to fn areall set to OFF to acquire the omitted map in which all bits are “0”,after which the process proceeds to step S4009.

Subsequently, a lower limit specifying/comparing process (step S4009)and an upper limit specifying/comparing process (step S4010) areexecuted. A detailed procedure of the lower limit specifying/comparingprocess (step S4009) and the upper limit specifying/comparing process(step S4010) will be described later.

The designating unit 2711 designates the compressed forms file Fi havinga numerical value within the numerical value range (step S4011). Thefile configuration data specifying unit 2109 then specifies a page listof the compressed forms file Fi having the numerical value within thenumerical value range (step S4012), and the process proceeds to stepS3621 of FIG. 36. Hence, a series of processes making up the numericalvalue retrieval executing process ends.

FIG. 41 is a flowchart of the lower limit specifying/comparing processof FIG. 40. The processes depicted in FIG. 41 are described withreference to the size comparison examples of FIGS. 28A to 28D.

As depicted in FIG. 28B, the logical product of the lower limitnumerical value group map (four-place/head numeral 3 map M43) and theomitted map M02 is calculated to acquire the lower limit map M03 (stepS4101). Subsequently, the file number i is set to 0, and the lower limitcomparison result map M04 is initialized (by setting all bits to OFF)(step S4102).

Whether the i-th bit in the lower limit map M03 is ON is determined(step S4103). When the i-th bit is OFF (step S4103: NO), the processproceeds to step S4110.

When the i-th bit is ON (step S4103: YES), the compressed forms file Fiis extracted from the compressed forms file F (step S4104). Followingthis, whether compressed information of an in-file numerical value(compressed information 2801 of FIG. 28B) is present in the compressedforms file Fi is determined (step S4105).

When the compressed information is present (step S4105: YES), a lowerlimit numerical value comparing process is executed (step S4106). Thelower limit numerical value comparing process will be described laterwith reference to FIG. 42. Based on the result of the lower limitnumerical value comparing process, whether a boundary condition by alower limit numerical value is satisfied is determined (step S4107).

When the boundary condition is not satisfied (step S4107: NO), theprocess returns to step S4105. When the boundary condition is satisfied(step S4107: YES), whether the i-th bit in the lower limit comparisonresult map M04 remains OFF is determined (step S4108). When the i-th bitis already ON (step S4108: NO), the process proceeds to step S4105.

When the i-th bit is OFF (step S4108: YES), the i-th bit is turned fromOFF to ON (step S4109), after which the process returns to step S4105.At step S4105, when no unchecked compressed information of an in-filenumerical value is present (step S4105: NO), the process proceeds tostep S4110. At step S4110, the file number i is increased by 1, andwhether i>n is satisfied is determined (step S4111).

When i>n is not satisfied (step S4111: NO), the process returns to stepS4103. When i>n is satisfied (step S4111: YES), the process proceeds tostep S4011 of FIG. 40. Hence, a series of processes making up the lowerlimit specifying/comparing process ends.

FIG. 42 is a flowchart of the lower limit numerical value check process.As depicted in FIG. 42, a two-byte/one-byte bit and a commapresence/absence bit in compressed information of a lower limitnumerical value and a two-byte/one-byte bit and a comma presence/absencebit in compressed information of an in-file numerical value are set toOFF (step S4201).

The compressed information is compared to determine whether feeders inthe information match (step S4202). When the feeders do not match (stepS4202: NO), the process proceeds to step S4107. When the feeders match(step S4202: YES), whether the number of places match is determined(step S4203).

When the number of places do not match (step S4203: NO), the processproceeds to step S4107. When the number of places also match (stepS4203: YES), a number of places counter N is set to N=Nmax (step S4204),which represents the number of places of the lower limit numerical valueand the number of places of the in-file numerical value.

Subsequently, whether a numeral in the N-th place in the in-filenumerical value is at least equal to a numeral in the N-th place in thelower limit numerical value is determined (step S4205). Being equal toor larger than the numeral in the N-th place in the lower limitnumerical value is adopted as a determination criterion because aboundary condition by the lower limit numerical value of a numericalvalue range is “≦”. If the boundary condition is “<”, whether thenumeral in the N-th place in the in-file numerical value is larger thanthe numeral in the N-th place in the lower limit numerical value isdetermined.

When the numeral in the N-th place in the in-file numerical value is notequal to or larger than the numeral in the N-th place in the lower limitnumerical value (step S4205: NO), the process proceeds to step S4107.When the numeral in the N-th place in the in-file numerical value isequal to or larger than the numeral in the N-th place in the lower limitnumerical value (step S4205: YES), the count of the number of placescounter N is decreased by 1 (step S4206), and whether the count N of thenumber of places counter N satisfies N<0 is determined (step S4207).When N<0 is not satisfied (step S4207: NO), whether a compressed codefor a decimal point between a compressed code for a numeral in the(N−1)-th place and a compressed code for a numeral in the n-th place isin only either the compressed information of the lower limit numericalvalue or in the compressed information of the in-file numerical value isdetermined (step S4208).

When the compressed code for the decimal point between the compressedcode for the numeral in the (N−1)-th place and the compressed code forthe numeral in the n-th place is not in only one of the compressedinformation (step S4208: NO), that is, when the compressed code for thedecimal point is present in both compressed information or when thecompressed code for the decimal point is absent in both compressedinformation, the process returns to step S4205.

When the compressed code for the decimal point between the compressedcode for the numeral in the (N−1)-th place and the compressed code forthe numeral in the n-th place is in only one of the compressedinformation (step S4208: YES), the process proceeds to step S4107.

When N<0 is satisfied at step S4207 (step S4207: YES), the processproceeds to step S4107. Hence, a series of processes making up the lowerlimit numerical value comparing process ends.

At step S4107 of FIG. 41, meeting the boundary condition by the lowerlimit numerical value is determined when N<0 is satisfied at step S4207(step S4207: YES), while not meeting the boundary condition by the lowerlimit numerical value is determined when determination of NO is given atstep S4202, step S4203, step S4205, or step S4208.

FIG. 43 is a flowchart of the upper limit specifying/comparing processof FIG. 40. The processes depicted in FIG. 43 are described withreference to the size comparison examples of FIGS. 28A to 28D.

As depicted in FIG. 28B, the logical product of the upper limitnumerical value group map (four-place/head numeral 6 map M46) and theomitted map M02 is calculated to acquire the upper limit map M05 (stepS4301). Subsequently, the file number i is set to 0, and the upper limitcomparison result map M06 is initialized (by setting all bits to OFF)(step S4302).

Whether the i-th bit in the upper limit map M05 is ON is determined(step S4303). When the i-th bit is OFF (step S4303: NO), the processproceeds to step S4310.

When the i-th bit is ON (step S4303: YES), the compressed forms file Fiis extracted from the compressed forms file F (step S4304). Followingthis, whether compressed information of an in-file numerical value(compressed information 2803 of FIG. 28C) is present in the compressedforms file Fi is determined (step S4305).

When the compressed information is present (step S4305: YES), an upperlimit numerical value comparing process is executed (step S4306). Theupper limit numerical value comparing process will be described laterwith reference to FIG. 44. Based on the result of the upper limitnumerical value comparing process, whether a boundary condition by anupper limit numerical value is satisfied is determined (step S4307).

When the boundary condition is not satisfied (step S4307: NO), theprocess returns to step S4305. When the boundary condition is satisfied(step S4307: YES), whether the i-th bit in the upper limit comparisonresult map M06 remains OFF is determined (step S4308). When the i-th bitis already ON (step S4308: NO), the process proceeds to step S4305.

When the i-th bit is OFF (step S4308: YES), the i-th bit is turned fromOFF to ON (step S4309), after which the process returns to step S4305.At step S4305, when no unchecked compressed information of an in-filenumerical value is present (step S4305: NO), the process proceeds tostep S4310. At step S4310, the file number i is increased by 1, andwhether i>n is satisfied is determined (step S4311).

When i>n is not satisfied (step S4311: NO), the process returns to stepS4303. When i>n is satisfied (step S4311: YES), the process proceeds tostep S4011 of FIG. 40. Hence, a series of processes making up the upperlimit specifying/comparing process is ended.

FIG. 44 is a flowchart of the upper limit numerical value check process.As depicted in FIG. 44, a two-byte/one-byte bit and a commapresence/absence bit in compressed information of an upper limitnumerical value and a two-byte/one-byte bit and a comma presence/absencebit in compressed information of an in-file numerical value are set toOFF (step S4401).

The compressed information is compared to determine whether feeders inthe information match (step S4402). When the feeders do not match (stepS4402: NO), the process proceeds to step S4307. When the feeders match(step S4402: YES), whether the number of places match is determined(step S4403).

When the number of places do not match (step S4403: NO), the processproceeds to step S4307. When the number of places also match (stepS4403: YES), a number of places counter N is set to N=Nmax (step S4404),which represents the number of places of the upper limit numerical valueand the number of places of the in-file numerical value.

Subsequently, whether a numeral in the N-th place in the in-filenumerical value is at most equal to a numeral in the N-th place in theupper limit numerical value is determined (step S4405). Being equal toor less than the numeral in the N-th place in the upper limit numericalvalue is adopted as a determination criterion because a boundarycondition by the upper limit numerical value of a numerical value rangeis “≧”. If the boundary condition is “>”, whether the numeral in theN-th place in the in-file numerical value is less than the numeral inthe N-th place in the upper limit numerical value is determined.

When the numeral in the N-th place in the in-file numerical value is notequal to or less than the numeral in the N-th place in the upper limitnumerical value (step S4405: NO), the process proceeds to step S4307.When the numeral in the N-th place in the in-file numerical value isequal to or less than the numeral in the N-th place in the upper limitnumerical value (step S4405: YES), the count of the number of placescounter N is decreased by 1 (step S4406), and whether the count N of thenumber of places counter N satisfies N<0 is determined (step S4407).When N<0 is not satisfied (step S4407: NO), whether a compressed codefor a decimal point between a compressed code for a numeral in the(N−1)-th place and a compressed code for a numeral in the n-th place isin only either the compressed information of the upper limit numericalvalue or in the compressed information of the in-file numerical value isdetermined (step S4408).

When the compressed code for the decimal point between the compressedcode for the numeral in the (N−1)-th place and the compressed code forthe numeral in the n-th place is not in only one of the compressedinformation (step S4408: NO), that is, when the compressed code for thedecimal point is present in both compressed information or when thecompressed code for the decimal point is absent in both compressedinformation, the process returns to step S4405.

When the compressed code for the decimal point between the compressedcode for the numeral in the (N−1)-th place and the compressed code forthe numeral in the n-th place is in only one of the compressedinformation (step S4408: YES), the process proceeds to step S4307.

When N<0 is satisfied at step S4407 (step S4407: YES), the processproceeds to step S4307. Hence, a series of processes making up the upperlimit numerical value comparing process ends.

At step S4307 of FIG. 43, meeting the boundary condition by the upperlimit numerical value is determined when N<0 is satisfied at step S4407(step S4407: YES), while not meeting the boundary condition by the upperlimit numerical value is determined when determination of NO is given atstep S4402, step S4403, step S4405, or step S4408.

As described above, according to the embodiment of the presentinvention, an intermediate numerical value group is detected and isreflected in the omitted map M02. Because of this, the presence/absenceof a numerical value within a numerical value range in a compressedforms file can be detected without carrying out matching check of thenumerical value within the numerical value range on the compressed formsfile specified by the appearance map of the intermediate numerical valuegroup.

Numerical value matching check is carried out only on the lowernumerical value group or the upper numerical value group. In carryingout matching check, because an in-file numerical value is linked to afeeder, numerical value information only can be retrieved at a highspeed from the compressed forms file Fi. Because matching check iscarried out between pieces of compressed information, size comparisoncan be carried out by comparing only the compressed codes for feedersand for the number of places for matching. This enables execution ofprecise retrieval at a high speed.

In the appearance frequency management data 500, the appearancefrequency of a numeral, etc., is revised. This increases the speed ofmatching check and decompression of a numerical value, and the increaseof the speed of checking and decompression is particularly effective ina case where numerical value data and character data are presenttogether in a file-to-be-retrieved.

The embodiment of the present invention thus offers an effect ofspecifying a file having a numerical value within a numerical valuerange while keeping the file in a compressed form to improve the speedand precision of numerical value range retrieval.

According to the embodiment, files-to-be-retrieved having a numericalvalue in a numerical value group satisfying the number of places and ahead numeral can be narrowed down before execution of numerical valuerange retrieval.

The embodiment increases the speed of the narrowing down offiles-to-be-retrieved having a numerical value in a numerical valuegroup satisfying the number of places and a head numeral.

According to the embodiment, numerical values can be compared in sizestep by step in a compressed form by carrying out comparison of thenumber of places, of head place numerals, second place numerals, etc.,in sequence.

According to the embodiment, the compression efficiency of a numericalvalue can be improved preferentially to be higher than the compressionefficiency of character data.

According to the embodiment, the compression efficiency of a numericalvalue having a comma can be improved preferentially to be higher thanthe compression efficiency of character data.

According to the embodiment, the compression efficiency of a numericalvalue having a decimal point can be improved preferentially to be higherthan the compression efficiency of character data.

According to the embodiment, a numerical value can be extracted at highspeed even from a file having character strings mixed with numerals.

According to the embodiment, compressed numerals are classified to ableto perform size comparison and numerical value range retrieval onnumerical values of the same type.

The embodiment enables determining the presence or absence of anumerical value within a numerical value range without carrying outnumerical value retrieval on numerical values in an intermediatenumerical value group. This speeds up numerical value retrieval.

The object and advantages of the invention will be realized and attainedby means of the elements and combinations particularly pointed out inthe claims.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory and arenot restrictive of the invention, as claimed.

All examples and conditional language recited herein are intended forpedagogical purposes to aid the reader in understanding the inventionand the concepts contributed by the inventor to furthering the art, andare to be construed as being without limitation to such specificallyrecited examples and conditions, nor does the organization of suchexamples in the specification relate to a showing of the superiority andinferiority of the invention. Although the embodiment(s) of the presentinventions have been described in detail, it should be understood thatthe various changes, substitutions, and alterations could be made heretowithout departing from the spirit and scope of the invention.

What is claimed is:
 1. A non-transitory computer-readable recordingmedium storing therein an information retrieval program that causes acomputer to execute: detecting a feeder indicative of a presence of anumerical value in a file subject to retrieval in which a numeral and acharacter are present together; detecting a number of places in thenumerical value correlated to the feeder detected at the detecting afeeder; and compressing the numerical value into compressed informationincluding a compression code for a numeral indicative of the number ofplaces detected at the detecting the number of places and a compressioncode for a numeral at each place in the numerical value, wherein thenumerical value is correlated to the feeder based on an appearancefrequency of a numeral included in the file.
 2. The non-transitorycomputer-readable recording medium according to claim 1, wherein: thefeeder is information that specifies a type of the numerical value. 3.The non-transitory computer-readable recording medium according to claim1, wherein: the information retrieval program further causes thecomputer to execute detecting the numerical value to be a two-bytenumerical value or a one-byte numerical value, the compressing includescompressing the numerical value into compressed information including acompression code for a result of detection at the detecting a two-byteor one-byte numerical value.
 4. The non-transitory computer-readablerecording medium according to claim 1, wherein: the informationretrieval program further causes the computer to execute detecting acomma included in the numerical value, and the compressing includescompressing the numerical value into compressed information including acompression code for a result of detection at the detecting a comma. 5.The non-transitory computer-readable recording medium according to claim1, wherein: the information retrieval program further causes thecomputer to execute revising an appearance frequency of a numeralpresent in the file to an appearance frequency higher than an appearancefrequency of a character present in the file, and the compressingincludes compressing the numerical value based on an appearancefrequency revised at the revising.
 6. The non-transitorycomputer-readable recording medium according to claim 1, wherein: therevising includes revising an appearance frequency of a comma present inthe file to an appearance frequency higher than an appearance frequencyof a character present in the file.
 7. The non-transitorycomputer-readable recording medium according to claim 1, wherein: therevising includes revising an appearance frequency of a decimal pointpresent in the file to an appearance frequency higher than an appearancefrequency of a character present in the file.
 8. An informationretrieval apparatus comprising: a first detecting unit that detects afeeder indicative of a presence of a numerical value in a file subjectto retrieval in which a numeral and a character are present together; asecond detecting unit that detects a number of places in the numericalvalue correlated to the feeder detected by the first detecting unit; anda compressing unit that compresses the numerical value into compressedinformation including a compression code for a numeral indicative of thenumber of places detected by the second detecting unit and a compressioncode for a numeral at each place in the numerical value, wherein thenumerical value is correlated to the feeder based on an appearancefrequency of a numeral included in the file.